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.
Description of problem:Environment Edit doesn't show prior environment shows "Click to Edit" and when clicked, shows Locker.
Version-Release number of selected component (if applicable):
78661810bb4fdca7e246e40e2e8e002e1c15cc59
How reproducible:
Always
Steps to Reproduce:
1. Navigate to Organizations
2. Add new Environment, prior locker
3. Add another Environment, prior previous
4. Edit new environment created in 3, see "Click to Edit" on third row for "Prior Environment"
Actual results:
See screenshot.
see "Click to Edit" on third row for "Prior Environment"
Expected results:
Expect to see prior env, such as Development if that were the previous.
Additional info:
After discussion, removed the ability to change the prior of an environment. It would cause too many issues with content, etc...
01f7075f07a6fb6985100ba8a1d64902d92269d5