Issue with tier price 0 when saving product second time

[keyurshah070]

Preconditions (*)

1.Fresh Magento 2.3.3 or any Magento 2.3 setup

Steps to reproduce (*)

1. Create a simple Test product
2. Set the normal price 100 or whatever you want
3. Set the tier price 0 for "All Groups" with "1" Qty.

4. Save the product
5. You can see the product tier price is 0 saved and on the frontend, you can see 0 prices which is expected

6. Edit the same product again from the backend.

7. Open the Advance pricing section and set the Tier price "10" for "All Groups" and "1" Qty.

8. Save the product

9. You can see "10" price on frontend and backend which is expected.

10. Now edit the product again from backend and open Advance pricing section

11. Set the price "0" for "All Groups" with "1" Qty.

12. Save the product

Expected result (*)

1. After saving the second time product price should be displayed which we are saving(In this case 0 should be display)

Actual result (*)

1. Price is showing the Non-zero price during the second time.

[m2-assistant]

Hi @keyurshah070. 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.3-develop instance - upcoming 2.3.x release

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

@keyurshah070 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @keyurshah070. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[m2-assistant]

Hi @krishprakash. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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-engcom-team]

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

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Shubham0492]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @Shubham-Webkul. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @Shubham-Webkul, here is your Magento instance.
Admin access: https://i-25195-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[slavvka]

Hi @keyurshah070. Thank you for your report.
The issue has been fixed in #26162 by @ravi-chandra3197 in 2.4-develop branch
Related commit(s):

• ffab78e0cb1c2a73ffbded3cda0c75cd0ff9542d
• ee152fcab0a5913d21d79ed4ced54a65c96f76bc
• 918fd028fd9d768946e52a4edbcbd4dc0a77a434
• f309ae042236736db0a964e533e33baa0a0e5142

The fix will be available with the upcoming 2.4.0 release.