Closed ivagarfitt closed 1 year ago
Hi @ivagarfitt. 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@magento I am working on this
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.
@magento give me 2.4.5-p2 instance
Hi @ivagarfitt. Thank you for your request. I'm working on Magento instance for you.
Hi @ivagarfitt, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
@magento give me 2.4.5-p2 instance
Hi @ivagarfitt. Thank you for your request. I'm working on Magento instance for you.
Hi @ivagarfitt, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
@magento give me 2.4.5-p2 instance
Hi @ivagarfitt. Thank you for your request. I'm working on Magento instance for you.
Hi @ivagarfitt, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
@magento give me 2.4.5-p2 instance
Hi @ivagarfitt. Thank you for your request. I'm working on Magento instance for you.
Hi @ivagarfitt, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.
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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @ivagarfitt,
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
As per Magento devdocs https://experienceleague.adobe.com/docs/commerce-admin/inventory/quantities/quantities-assign-per-product.html?lang=en. After adding sources, update the inventory quantities for your product. These values track the on-hand, available stock amounts.We have to update stock status even though if we set Set all Default Quantities to 0 the child product will be in instock only we have to make it as out of stock after the parent bundle product will go to out of stock.
Thanks
Have you tested for a Bundle parent product?
Because after child goes out of stock and makes parent Out of Stock you cannot get parent "In stock" even if all the children are back in stock unless you add Qty to a parents for a Default stock. If you change it to "In stock" manually, next time you create shipment using API it will check status against default source and turn it back to "Out of stock"
I can see that is looking fixed in 2.4.6
Hi @ivagarfitt,
Thanks for your update.
We have verified for Bundle Parent product also it is working as expected.As per comment https://github.com/magento/magento2/issues/37684#issuecomment-1618830558 the seems to be fixed please let us know can we close this issue?
Thanks.
Hi @ivagarfitt,
We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.
Thanks.
Preconditions and environment
Steps to reproduce
Expected result
Bundle product parent that had Stock status auto changed to "Out of stock" to auto change to "In Stock" when children product updated with positive Qty.
Actual result
Bundle product parent that was auto changed to "Out of stock" not auto changing to "In stock" when all children having positive stock.
Reason: Bundle product status only auto change to "In stock" when positive Qty is added to Default source against the parent!
Additional information
Default source Qty not impacting children Stock status because if we update Qty using inventory/sorce-items API status is properly updated.
However status update for the parent using same API does nothing if Default source is having Qty=0
Release note
No response
Triage and priority