Magento backend catalog "Cost" without currency symbol

[mage2pratik]

Preconditions (*)

1. Magento 2.3.X
2. Magento 2.2.X

Steps to reproduce (*)

1. Navigate to admin catalog product grid
2. Using "Columns" selection add 'Cost' column in the grid

Expected result (*)

1. "Cost" will be shown with currency code

Actual result (*)

[magento-engcom-team]

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

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

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

• yes
• no

[mage2pratik]

@magento-engcom-team give me 2.3 instance

[mage2pratik]

#MM19IN

[magento-engcom-team]

✅ Confirmed by @mage2pratik
Thank you for verifying the issue! 👍 Your confirmation will help us to acknowledge and process this report.

[mage2pratik]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98037, MAGETWO-98038 were created

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

[swnsma]

#20472

[jtomka]

#mlau

[jtomka]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

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

• ee8868922bd027510c707a092d2c0f0d04019b71

The fix will be available with the upcoming 2.2.9 release.

[orlangur]

Still not fixed properly. Currently merged PRs must be reverted.

Proper fix does require changing columns displayed in grid by default and will also cover #20472 and #21910.

[imrandotftr]

"I am working on this at #dmcdindia19”

[magento-engcom-team]

@imrandotftr thank you for joining. Please accept team invitation here and self-assign the issue.

[m2-assistant]

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

[magento-engcom-team]

Hi @mage2pratik, @orlangur, @imrandotftr.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.3.3 release.

[slavvka]

Hi @mage2pratik. Thank you for your report.
The issue has been fixed in #27261 by @sergiy-v in 2.4-develop branch
Related commit(s):

• d81d1d451bb7f10492d249e2c0c70e9d8d1df905

The fix will be available with the upcoming 2.4.0 release.