Closed mahendra1988 closed 5 years ago
Hi @mahendra1988. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.
@mahendra1988 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @engcom-backlog-andrii. 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: :point_down:
[ ] 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
branchDetails
- 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.
Hi @mahendra1988. Thanks for the report, this can be a feature request. It will be processed faster if you move this to https://github.com/magento/community-features
Hi, thanks to stop to send me this thread
Le jeudi 29 novembre 2018, Magento Community Engineering < notifications@github.com> a écrit :
Hi @engcom-backlog-andrii https://github.com/engcom-backlog-andrii. 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: 👇
-
Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result). DetailsIf 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.
-
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.
Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
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!
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
Add label Issue: Confirmed once verification is complete.
Make sure that automatic system confirms that report has been added to the backlog.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/19456#issuecomment-442808088, or mute the thread https://github.com/notifications/unsubscribe-auth/AAnwS8xllMkpiKR6DACpUGc1RposOyXGks5uz8vjgaJpZM4Y5gki .
Description (*)
Admin backend menus does not showing any direction or navigation icos as magento provide in frontend.
Expected behavior (*)
Show the navigation icos as its show in frontend.
Benefits
Admin will easily get an idea that this Menu have sub-menus or not so he will have idea about sub-menus.
Additional information