[GraphQL][Wishlist] Unable to add wishlist items with customizable options to cart

[Syamsg]

Preconditions and environment

1. Magento version: 2.x.x (specify exact version, e.g. 2.4.8)
2. PHP version: (e.g. 8.1)
3. Elasticsearch/OpenSearch version: (if relevant)
4. Environment: (e.g. local/dev/staging, Docker, WSL, etc.)

Steps to reproduce

1. Add a product with customizable options to the wishlist using GraphQL mutation addProductsToWishlist.

mutation AddToWishlist {
    addProductsToWishlist(
        wishlistId: "90"
        wishlistItems: [
            {
                sku: "24-UG05"
                quantity: 1
                selected_options: []
                entered_options: [
                    { uid: "Y3VzdG9tLW9wdGlvbi8yNw==", value: "19" }
                    { uid: " Y3VzdG9tLW9wdGlvbi81Mw==", value: "30" }
                ]
            }
        ]
    ) {
        wishlist {
            id
            items_count
            items {
                id
                product {
                    name
                }
            }
        }
    }
}

2. Attempt to add the wishlist item to the cart using the GraphQL mutation addWishlistItemsToCart.

mutation {
    addWishlistItemsToCart(wishlistId: 90, wishlistItemIds: ["917"]) {
        status
        add_wishlist_items_to_cart_user_errors {
            wishlistItemId
            code
            message
        }
    }
}

Expected result

The wishlist product is properly added to the cart along with the customizable options selected in the wishlist.

Actual result

The mutation does not return an error, but the customizable options are not added properly — only the base product is added to the cart without the selected customizable options.

Additional information

Using GraphQL, I'm unable to add a product with customizable options to the cart from the wishlist — only the base product is added, and the selected options are not included.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Syamsg. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @Syamsg ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4-develop and 2.4.8 instances by following the provided steps and preconditions. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:

1. Add a product with customizable options to the wishlist using GraphQL mutation addProductsToWishlist.

mutation AddToWishlist {
    addProductsToWishlist(
        wishlistId: "90"
        wishlistItems: [
            {
                sku: "24-UG05"
                quantity: 1
                selected_options: []
                entered_options: [
                    { uid: "Y3VzdG9tLW9wdGlvbi8yNw==", value: "19" }
                    { uid: " Y3VzdG9tLW9wdGlvbi81Mw==", value: "30" }
                ]
            }
        ]
    ) {
        wishlist {
            id
            items_count
            items {
                id
                product {
                    name
                }
            }
        }
    }
}

2. Attempt to add the wishlist item to the cart using the GraphQL mutation addWishlistItemsToCart.

mutation {
    addWishlistItemsToCart(wishlistId: 90, wishlistItemIds: ["917"]) {
        status
        add_wishlist_items_to_cart_user_errors {
            wishlistItemId
            code
            message
        }
    }
}

Therefore, we are marking this ticket as "Issue: Confirmed."

Thank You!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14850 is successfully created for this GitHub issue.