Product Advanced Pricing design issue

[saphaljha]

Preconditions (*)

1. Install the newest version 2.3.X

Steps to reproduce (*)

1. Add new product
2. Add new tierprice

Expected result (*)

Actual result (*)

[magento-engcom-team]

Hi @saphaljha. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[magento-engcom-team]

Hi @speedy008. 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[sidolov]

Hi @saphaljha. Thank you for your report.
The issue has been fixed in #18790 by @ashutoshwebkul in 2.3-develop branch
Related commit(s):

• 6bb825873812cff3ab77d71f1f3542d40aae2b85

The fix will be available with the upcoming 2.3.1 release.

[speedy008]

Hi @engcom-backlog-nazar
I have started working on 2.3x Instance to resolve this issue.

[ghost]

Hi @speedy008 this issue fixed in 2.3-develop, just leave this open.

[magento-engcom-team]

@engcom-backlog-andrii Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96739 were created

[ghost]

Hi @saphaljha , thank you for you report, this issue has already fixed in 2.3-develop branch, and will be available on 2.3.1 release.

[magento-engcom-team]

Hi @saphaljha. Thank you for your report.
The issue has been fixed in #21229 by @mage2pratik in 2.2-develop branch
Related commit(s):

• 079d5d5f99f1cd6db5d03fb1adba3e685fd3b8f9

The fix will be available with the upcoming 2.2.9 release.