Grouped Product Frontend Quantity Validations are Missing

[Mohamed-Asar]

Preconditions and environment

• Magento version 2.4.7-p3

Steps to reproduce

1. Create a Grouped Product and associate it with child products.

2. Set the following quantity properties for one of the child products:

   • Minimum Qty Allowed in Shopping Cart: 2
   • Maximum Qty Allowed in Shopping Cart: 10
   • Qty Increments: 2

3.Open the Product Detail Page (PDP) of the Grouped Product and test invalid quantities for the selected child product (e.g., 1, 3, or 11) to confirm that invalid inputs are restricted.

Expected result

The validation error should be displayed upon clicking the "Add to Cart" button, without reloading the page, similar to the behavior on the Simple Product PDP.

Actual result

Instead of displaying the error immediately, the page reloads and the error is shown afterward from the server side.

Additional information

No response

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 @Mohamed-Asar. 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.

[Mohamed-Asar]

@magento i'm working on this

[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 @Mohamed-Asar,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop Magento instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create a Grouped Product and associate it with child products.
• Set the following quantity properties for one of the child products:

1. Minimum Qty Allowed in Shopping Cart: 2
2. Maximum Qty Allowed in Shopping Cart: 10
3. Qty Increments: 2

• Open the Product Detail Page (PDP) of the Grouped Product and test invalid quantities for the selected child product (e.g., 1, 3, or 11) to confirm that invalid inputs are restricted.

Instead of displaying the error immediately, the page reloads and the error is shown afterward from the server side.

Hence Confirming the issue.

Thanks.