Bundle product: incorrect child item invoice_qty when dynamic price is set to false

[Emanuel-23]

Preconditions (*)

1. Fresh Magento 2.3.5 or 2.3.6 Open Source (also reproducible on 2.4-develop) with at least 2 simple products that are in stock (optionally: demo content)
2. Access to database tables (we want so look into the table sales_order_item)

Steps to reproduce (*)

1. Create a new bundle product via Magento 2 administration
   1.1. Change "Dynamic Pricing" setting to false
   1.2. Add a price i.e. 75 $
   1.3. Perhaps not relevant, but in my use case: [Add visible to "not visible individually"]
   1.4. Add bundle options with setting "ship bundle items" set to "together"
   
   1.4.1. Add one bundle option with a name of your choice of input type "checkbox" and set to "required"
   1.4.2. Add two simple products of your choice (i.e. ID 1 and ID 2 of the demo content products)
   1.4.3. Change the qty settings of the simple products to a qty > 1 (i.e. 2 and 3)
   1.4.4. leave the price range setting on "fixed"
   1.4.5. Mark the checkbox "is Default"
   1.5. Save the product
2. Create a new order via Magento 2 administration
   2.1. Add the new bundle product to your order
   
   2.2. Click on configure and only change the qty to 2
   2.3. Save the product items (uncheck the discount if it has been set, but dont recalculate)
   2.4. Add a payment of your choice
   2.5. Add a shipping of your choice
   
   2.6. Save the order
3. Create a new invoice via Magento 2 administration
   3.1. Skip the shipping procedure entirely, just create an invoice
   3.2. Leave all settings as is
   3.3. Save the invoice
   
4. Check the database table sales_order_items selected on the order number (order id gets in parent_id column)
   
   (in our case the database values should be displayed in an pdf invoice, which also reflect the wrong qty's)

--> the order_qty has correctly been changed, but the invoice_qty has not been changed correctly and refers to the parent items qty... see screenshots in the following sections

Expected result (*)

1. After creating the invoice the simple items within the bundle should have exactly that qty that has been defined in the bundle option qty
2. After the saved invoice the column invoiced_qty of the bundled child items (the simple items of the bundle) whitin sales_order_items should also reflect that (actually they should be exactly the same as in ordered_qty in the same table)
   

Actual result (*)

1. After creating the invoice the simple items within the bundle actually have the wrong qty - the qty of the parent item (the bundle item) instead.
   

Additional notes:

this does NOT happen when changing the dynamic price to true!!

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @Emanuel-23. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Delta. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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]

We confirm that the issue is reproducible on the latest 2.4-develop

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-38953 were created

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.