-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typo Issue and Missing header title at Customer Sales order grid #22641
Comments
Hi @vishal-7037. Thank you for your report.
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:
For more details, please, review the Magento Contributor Assistant documentation. @vishal-7037 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @vishal-7037. Thank you for working on this issue.
|
I am working on this at #dmcdindia19 |
Hi @shikhamis11. Thank you for working on this issue.
|
Hi @webkul-ajaysaini. Thank you for working on this issue.
|
I am working on this at #dmcdindia19” |
✅ Confirmed by @rogyar Issue Available: @rogyar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
@magento-engcom-team give me 2.2-develop instance |
Hi @rogyar. Thank you for your request. I'm working on Magento 2.2-develop instance for you |
Hi @rogyar, here is your Magento instance. |
Hi @vishal-7037. Thank you for your report. The fix will be available with the upcoming 2.3.3 release. |
There are typo errors found on the Magento admin panel. Please review Customer Sales order grid. You will find typo error for the order column header. In the Sales invoice grid, the header title of a column is 'Order #' and here it is 'Order'. they should be the same.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: