Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1212506 [details]
Screenshot of Resources in Manager Role has permissions by default

Description of problem:
Content and Container resource filters are not present by default in Manager Role. So the user has to add those permission manually each time while creating an Org Admin or even manager with those extra permissions. Just to ease the customer headache.

Version-Release number of selected component (if applicable):
Satellite 6.3 Snap 5

How reproducible:
Always

Steps to Reproduce:
1. From Administer -> Roles, edit/view inbuilt Manager Role.
2. Create a Org Admin by cloning this manager role.
3. See what are permissions available in Cloned Role(or Org Admin)

Actual results:
The Resource filters for Content and Containers are missing as its not available in Manager role itself from which we cloned this org admin role. Or one has to manually add them all.

Expected results:
Add Content and Container resource type permissions by default in Manager role.

Additional info:

*** This bug has been marked as a duplicate of bug 1304608 ***