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.

Description of problem:
When adding a permission to a Organization the cancel element (or button) appears out of place.

How reproducible:
When navigating, permission for +All the Cancel button will appear next to Permission For, also missing [<< Previous button]
When Selecting +All followed by [Next>>] the Cancel button appears next to Permission For.


Steps to Reproduce:
1. Navigate to Roles.
2. Select a Role or create a new role.
3. Select Permissions.
4. Select a Permission
5. Select Add Permission
6. At this point, Select +All or +All followed by Next
  
Actual results:
[Cancel] button appears out of place located near Text Permission For.
Also, Note if you simply select +All you will find there is no [previous] button however the Cancel button does appear, again next to Permission For:.

Expected results:
Cancel button should be placed appropriately.  User experience should remain consistent through out workflow.

39f8b775874318009441886c16c2c2dc8a6ed4f2

This adds extra text to indicate to the user to use the cancel button to return to picking an individual resource type and moves the Cancel button to a more logical location.

QA Verified

getting rid of 6.0.0 version since that doesn't exist