magento2
magento2 copied to clipboard
Configurbale Product update child product saving qty move issue
Preconditions and environment
- Magento version - 2.4.6
- Anything else that would help a developer reproduce the bug
Steps to reproduce
I edited the configurations for “Tshirt” and saved.
Also, after saving with new configuration options selected, the inventory from one child product was moved to one of the new child products. This will be a big problem for our inventory.
Please see below photos and video
Existing stock was 8.0 Fit 1 = qty 2 10.0 Fit 1 = qty 2
After adding new options, 8.0 Fit 1 inventory qty was moved to 10.0 Fit 2
Note : This is issue faced only when quantity per source enable.
Expected result
Qty not need moved but here, moved when save configurable product.
Actual result
Child product qty moved when update with add new child option
Additional information
Here, i attached both screen shot. before and after. here 3 qty moved
Release note
No response
Triage and priority
- [X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- [X] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Hi @amarishcws. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
-
@magento give me 2.4-develop instance
- upcoming 2.4.x release - 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
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: :point_down:
- [ ] 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
branchDetails
- Add the comment@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-develop
branch, please, add the labelReproduced 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.
@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering Admin access: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering/admin_8ae2 Login: e5e76345 Password: 10c7632e3b84
Hi @amarishcws,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.
Steps to reproduce
I edited the configurations for “Tshirt” and saved.
Also, after saving with new configuration options selected, the inventory from one child product was moved to one of the new child products. This will be a big problem for our inventory.
Please see below photos and video
Existing stock was 8.0 Fit 1 = qty 2 10.0 Fit 1 = qty 2
QTY is not moved to another product of the QTY after saving the configurable product.
Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.
Thanks.
hi @engcom-Bravo
I have faced this issue in magento 2.4.6 p3 version. see the attached video
Please provide us your store admin. so, i will create product and give you steps.
Note : i have faced this issue when edit configuration with add new child product attribute and save the product
@magento give me 2.4-develop instance
hi @engcom-Bravo Have u check ?
@magento @daipham31 Have u check ?
@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering Admin access: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering/admin_d53d Login: cea4774e Password: 0275984d45ba
Hi @amarishcws,
Thanks for your update.
We have verified the issue here and the issue is not reproducible and quantity is not moving while saving configurable product.
Can you please check the issue https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering/admin_d53d/admin/dashboard/ and let us know if we are missing anything.
If the instance is timeout please request with comment @magento give me 2.4-develop instance you will get a new instance.
Thanks.
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
@engcom-Bravo see the attached screen shot and video. this issue faced when scope is enable and edit configuration for configurable product
Uploading whatsapp-video-2024-01-08-at-44836-pm-1_ihqkvtUD.mp4…
@engcom-Bravo see the attached screen shot and video. this issue faced when scope is enable and edit configuration for configurable product
https://github.com/magento/magento2/assets/97889594/7dbfe329-dfce-4b38-9033-8810f9ea820d
@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering Admin access: https://996374af42d2f7766a651384cb74e926.instances-prod.magento-community.engineering/admin_5e55 Login: bdd3ecb3 Password: 2548ebf87803
Hi @amarishcws,
Thanks for your update.
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.
Steps to reproduce
I edited the configurations for “Tshirt” and saved.
Also, after saving with new configuration options selected, the inventory from one child product was moved to one of the new child products. This will be a big problem for our inventory.
Please see below photos and video
Existing stock was 8.0 Fit 1 = qty 2 10.0 Fit 1 = qty 2
The Quantity was moved to another variation of the Configurable Product.
Hence Confirming the issue.
Thanks.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-10805 is successfully created for this GitHub issue.
:white_check_mark: 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.
@m2-community-project any update ?
@engcom-Bravo @m2-community-project I am waiting for your reply. Please give update.
Hi @amarishcws,
The Jira is still in Implementation state.we will provide updates here soon.
Thanks.
@engcom-Bravo @m2-community-project I am waiting for your reply. Please give update.
@engcom-Bravo @m2-community-project I am waiting for your reply. Please give update.
@engcom-Bravo @m2-community-project I am waiting for your reply. Please give update.