Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

39586 Submenu group title not appearing in Marketing menu #39732

Open
wants to merge 1 commit into
base: 2.4-develop
Choose a base branch
from

Conversation

ajay2108
Copy link

Description (*)

Submenu group title not appearing in Marketing menu - Admin Panel

Related Pull Requests

Manual testing scenarios (*)

  1. Go to admin panel and review USER CONTENT sub-menu in Marketing menu by clicking Marketing menu.
  2. You can see "USER CONTENT" sub-menu title.

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Copy link

m2-assistant bot commented Mar 12, 2025

Hi @ajay2108. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@ajay2108
Copy link
Author

@magento run all tests

1 similar comment
@ajay2108
Copy link
Author

@magento run all tests

@engcom-Bravo engcom-Bravo added the Priority: P3 May be fixed according to the position in the backlog. label Mar 14, 2025
@ajay2108
Copy link
Author

@engcom-Bravo - Please verify above PR. It is showing failure of some automatic checks which are not related to my commit. Can you please have a look and let me know if anything is required from my end.

@ajay2108
Copy link
Author

@engcom-Bravo - Did you get chance to have a look on this PR?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Priority: P3 May be fixed according to the position in the backlog.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants