Bundle with only not required options is not possible to be added to cart "Please specify product option(s)."

[abdel-aouby]

Preconditions and environment

• Magento version 2.4.8-p3 (The issue seems to be reproducible since Magento 2.4.3 and maybe even before)
• php 8.4 and 8.3

Steps to reproduce

1. Create a bundle product with the dynamic price OFF and two simple product options, with the entry being a radio button type, and uncheck the "Required" option.

2. Try to add the bundle product to the cart without selecting any of the options, use "none."

2. Try to add the bundle product to the cart without selecting any of the options, use "none."

Expected result

The product is added to the cart with 2000$ price

Actual result

The product is never added to the cart, and an error message is displayed
Please specify product option(s).

Additional information

This seems to be happening with all cases:
no matter if the price is dynamic or not
no matter if the type of the option is a "radio button" or a "checkbox"

The only condition is to have only one option, which should not be required

The issue seems to be reproducible since Magento 2.4.3

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 @abdel-aouby. 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-Bravo. 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-Bravo]

Hi @abdel-aouby,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.Kindly refer the screenshot.

The product is never added to the cart, and an error message is displayed.Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

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