Skip to content

[Issue] Improve user experience with roles tree #39654

Open
@m2-assistant

Description

@m2-assistant

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: Admin UIComponent: AdminIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.Reported on 2.4.xIndicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branch

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions