Wrong Order Status for Bundle Product Partial Credit memo

[github-jira-sync-bot]

 

Steps to reproduce:

1. Login to admin and Create any Bundle Product or use existing Bundle Product 
2. In the storefront or from backend, place an order with this a bundle product keeping qty greater than 1
3. Go to admin and open that order from Sales->Order and Create an Invoice. Observe the Order status, it is "Processing" 
4. Create a Partial Credit memo i.e do not refund for all the qty or all the products in Bundle
5. Check the Order status, it is "{}Complete{}" now.

(x) Actual result:

After creating partial Credit memo for order containing Bundle Product, the order status is "Complete"

(/) Expected result:

After creating partial Credit memo for order containing Bundle Product, the order status should be  "Processing"

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1714

[m2-assistant]

Hi @github-jira-sync-bot. 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.
⚠️ 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.

[chittima]

Internal team is working on this issue

[chittima]

Issue is fixed and here is the commit id:f977b49