JS validate: show many messsages for Bundle product with checkbox option

[hoangnm89]

Preconditions (*)

1. Fresh Magento 2.3.4

Steps to reproduce (*)

1. Create bundle product
2. Add option. Option Name: anything; Input Type: Checkbox; Required
3. Add product to Option
4. Add to cart on store front.
5. From validate if no option selected.
   

Expected result (*)

1. JS should validate and show one error message for Option

Actual result (*)

1. Show many messages
   

[m2-assistant]

Hi @hoangnm89. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@hoangnm89 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @krishprakash. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[krishprakash]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-27489-2-4-develop.instances.magento-community.engineering/admin_db57
Login: 786f1873 Password: 2f3a81208d18
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-32888 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[krishprakash]

Here is the similar issue for Wish list #26898

[m2-assistant]

Hi @neerajchand. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[neerajchand]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @neerajchand. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @neerajchand, here is your Magento instance.
Admin access: https://i-27489-2-4-develop.instances.magento-community.engineering/admin_8bc1
Login: d03137ef Password: a7f8bbd9e907
Instance will be terminated in up to 3 hours.

[ProkopovVitaliy]

@neerajchand Do you still work on it ?

[ProkopovVitaliy]

As there are no activity about 2 weeks i want to continue fix this issue.

[magento-engcom-team]

Hi @hoangnm89. Thank you for your report.
The issue has been fixed in #27854 by @ProkopovVitaliy in 2.4-develop branch
Related commit(s):

• bdeb9343e3235a7b837d959abaf3d5dddbec12bc
• e2244427a280ce57de69d78b98bdba2ce25a9165
• 6c7a5d4fa51a297a0f646b2be05e4bcbb2e500cf
• 8056d0e488158102dec20b72a5ec647d609fcca6
• 999fb8f98071ccedd3ccedaa833f4302355a0e75
• bf1722a676bcdeb15772c2e7d86054a9273e768e
• 628beb036b17e174bf58778c0b19e298b1e80f11
• 698ec67b8e617e616ba7ccbfe47d4da28ee3b185
• 90ee4132bf6fb717df1e452a7df5f240a31fd905
• 1046d8fcbf87468878775e064c1985c8a6e217cf
• 5a8eb6372ca81abe7c7c414da39be6416c57e7c8
• f46bed1108b0a43c52a8e2cab51dbc557f3cfa31
• f048e3a1b14e03574dabfb5995fe36da9adf816e
• 9a0e4df01bfa18f812bd7ee3897843f19c158438
• 6b9bf69c9f67a6c21efd72b6050f132dcc04f4fe
• 2fe917400dedd18b2bd061c4b39f35ee1f6691dc
• 382cac47fdfd215a1a724654096353beef9df450
• 00f3514c6e4391ab2c1039e5dccbb70eeb719623
• 497fce21444c9ecc56a935bf6af80fd937a8c567
• 9b11cbc9646ac69a11ad5e68ad88dceb9ccd8e7e
• 82dd19e51cd0e3c666bb0616af91aaa6be65b36c

The fix will be available with the upcoming 2.4.1 release.