Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Unless the logged in user has admin privileges for themselves, the 'Environments' tab of user edit should limit choice of new default env to ones in which the user already has the 'Register Systems in Environment' permissions.
This is more complicated than it first appears: Should unselectable envs be grayed out (currently Locker is not grayed out, even though it is never selectable)? What if an org has no envs that the user has register permission in, should it be included in the org choice selector?
I'm under the opinion that all orgs that the user is registered in, and all envs that each of those orgs has, should be visible. This would facilitate the call to their admin requesting privileges, as well as giving them context of the env progressions (ie. dev -> qa etc.).