Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grouped Product Wishlist Validations are not working #39496

Open
5 tasks
Mohamed-Asar opened this issue Dec 20, 2024 · 6 comments · May be fixed by #39497
Open
5 tasks

Grouped Product Wishlist Validations are not working #39496

Mohamed-Asar opened this issue Dec 20, 2024 · 6 comments · May be fixed by #39497
Assignees
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@Mohamed-Asar
Copy link
Contributor

Preconditions and environment

  • Magento 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 grouped product PDP, Don't fill any Qty or fill any invalid inputs like(-1, 3, 11)
  4. Click add to wishlist

Expected result

it should validate the inputs like simple product

image

Actual result

Adding products to wishlist and displaying price as zero, if negative Qty entered, wishlist displaying negative value in price

image

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”.
Copy link

m2-assistant bot commented Dec 20, 2024

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.


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
Copy link
Contributor Author

@magento i'm working on this

@engcom-Bravo engcom-Bravo added the Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. label Dec 20, 2024
@engcom-Bravo engcom-Bravo self-assigned this Dec 20, 2024
Copy link

m2-assistant bot commented Dec 20, 2024

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.

@Mohamed-Asar Mohamed-Asar linked a pull request Dec 20, 2024 that will close this issue
5 tasks
@engcom-Bravo
Copy link
Contributor

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:
  • Minimum Qty Allowed in Shopping Cart: 2
  • Maximum Qty Allowed in Shopping Cart: 10
  • Qty Increments: 2
  • Open grouped product PDP, Don't fill any Qty or fill any invalid inputs like(-1, 3, 11)
  • Click add to wishlist

Without any Quantity :

Screenshot 2024-12-20 at 10 39 42 am

With Negative Quantity :

Screenshot 2024-12-20 at 10 40 25 am

Adding products to wishlist and displaying price as zero, if negative Qty entered, wishlist displaying negative value in price.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: Catalog labels Dec 20, 2024
@github-jira-sync-bot
Copy link

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

Copy link

m2-assistant bot commented Dec 20, 2024

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Catalog Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants