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] Missing section when custom role is selected #35506

Closed
5 tasks done
m2-assistant bot opened this issue May 20, 2022 · 0 comments · Fixed by #35439
Closed
5 tasks done

[Issue] Missing section when custom role is selected #35506

m2-assistant bot opened this issue May 20, 2022 · 0 comments · Fixed by #35439
Assignees
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done

Comments

@m2-assistant
Copy link

m2-assistant bot commented May 20, 2022

This issue is automatically created based on existing pull request: #35439: Missing section when custom role is selected


Description (*)

When we select custom "Roles Resources" then we don't see "Magento Web API" under "Store>Configuration>Services"

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Login to Magento Admin as Administrator
  2. Navigate to "Store>Configuration>Services"
  3. You should be able to see "Magento Web API"
  4. Now set a custom permission by navigating to "System>User Roles"
  5. Select Administrators
  6. Go to Role Resources Tab
  7. Under "Resource Access" select Custom
  8. Now select every checkbox and save the role
  9. Navigate to "Store>Configuration>Services"
  10. You will see "Magento Web API" section is missing
  11. After applying this fix it will remain

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)
@m2-assistant m2-assistant bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label May 20, 2022
@m2-community-project m2-community-project bot added this to Ready for Development in High Priority Backlog May 20, 2022
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in High Priority Backlog May 20, 2022
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in High Priority Backlog Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done
Projects
Development

Successfully merging a pull request may close this issue.

1 participant