Cannot ship products that have less than 1 qty

[kevinruscoe]

Preconditions and environment

• Magento version
  2.4.5-p1

• Anything else that would help a developer reproduce the bug
  Clean install, no additional modules.

Steps to reproduce

1. Create a new product.
2. Set the "Minimum Qty Allowed in Shopping Cart" to 0.25 and the "Qty Uses Decimals" to "Yes".
3. Create a new order, adding the newly created product to the order, with the qty set to 0.5.
4. Click "Ship" within the order.

Expected result

A shipment is made, with a product with the quantity of 0.5 .

Actual result

The "Items to Ship" table will be blank. Clicking "Submit Shipment" gives the error "Shipment Document Validation Error(s): You can't create a shipment without products."

Additional information

I discovered this problem when upgrading from 2.4.3-p1 to 2.4.4-p2, but it also exists on 2.4.5-p1.

Invoices seem to get generated fine with 0.5 being invoiced, and orders with 1.5 works.

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

[m2-assistant]

Hi @kevinruscoe. 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.

[kevinruscoe]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @kevinruscoe. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @kevinruscoe, here is your Magento Instance: https://e303da01ca371fd514cd7f754cf5266b.instances.magento-community.engineering
Admin access: https://e303da01ca371fd514cd7f754cf5266b.instances.magento-community.engineering/admin_139e
Login: f0fb7e22
Password: 71fcf516d5d4

[kevinruscoe]

So, this seems fine in the dev branch (see order 000000003).

[m2-assistant]

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

     - 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[kevinruscoe]

It looks like #36411 was the fixed PR

[kevinruscoe]

Just confirming that #36411 fixes the problem.