Skip to content
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

[Issue] Improve user experience with roles tree #39654

Open
5 tasks done
m2-assistant bot opened this issue Feb 24, 2025 · 3 comments · May be fixed by #36511
Open
5 tasks done

[Issue] Improve user experience with roles tree #39654

m2-assistant bot opened this issue Feb 24, 2025 · 3 comments · May be fixed by #36511
Labels
Area: Admin UI Component: Admin Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@m2-assistant
Copy link

m2-assistant bot commented Feb 24, 2025

This issue is automatically created based on existing pull request: #36511: Improve user experience with roles tree


Description

When working with the roles tree, it's easy to get lost with the long list of possible options. This pull request adds buttons to collapse all, expand all, and expand branches with selected items. This functionality is similar to that provided in the category tree (Catalog -> Inventory -> Categories).

Manual testing scenarios

  1. Navigate to a list of roles in the admin
    • System -> Extensions -> Integrations -> [Edit, or Add New Integration] -> Basic Settings -> API -> Available APIs -> Resources
    • System -> Permissions -> User Roles -> [Edit, or Add New Role] -> Role Information -> Role Resources -> Roles Resources -> Resources
  2. Select a few items from the list. For best effect, choose one or two deeply nested items from different branches.
  3. Take a concise screen-shot showing which top-level areas the role / integration will have access to. (Note the 'collapse all' button.)
  4. Select a new item from a previously unused branch. (Note the 'expand all' button.)
  5. Take a concise screen-shot showing which exact permissions the role / integration will have access to. (Note the 'collapse all' and 'expand selected' buttons.)

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)
@m2-assistant m2-assistant bot added the Priority: P3 May be fixed according to the position in the backlog. label Feb 24, 2025
@m2-assistant m2-assistant bot linked a pull request Feb 24, 2025 that will close this issue
6 tasks
@engcom-Bravo
Copy link
Contributor

Confirming this issue as a Enhancement.

@engcom-Bravo engcom-Bravo added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: Admin Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Reported on 2.4.x Indicates original Magento version for the Issue report. Area: Admin UI labels Feb 24, 2025
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14020 is successfully created for this GitHub issue.

Copy link
Author

m2-assistant bot commented Feb 24, 2025

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Admin UI Component: Admin Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants