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:
In the Changeset History view, user can click one of the other user-created environments to view changesets that exist there. However, trying to click Locker fails to take user back to that view.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a new environment, "Dev", in ACME_Corporation
2. Content Management > Promotions.
3. Create a new changeset ("TestChangeset") and promote it to dev
4. Content Management > Changeset History; note that default environment is locker
5. Click "Dev" in the Environment path UI element, observing the correct promotion of your TestChangeset
6. Click Locker in the Environnment path UI element.
Actual results:
Locker never changes color
User cannot click through locker
Expected results:
User should be able to nav to Locker just like any other env.
Additional info:
Note: workaround is to simply do Content Management > Changeset History again, but that's still disjointed. User should be able to traverse the environment paths.
This is now fixed in master : 01d22151a351ab75f68482c72e226f1abef41610
You should never be taken to locker on this page, except if locker is the only environment (and nothing would show up anyways).
Description of problem: In the Changeset History view, user can click one of the other user-created environments to view changesets that exist there. However, trying to click Locker fails to take user back to that view. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a new environment, "Dev", in ACME_Corporation 2. Content Management > Promotions. 3. Create a new changeset ("TestChangeset") and promote it to dev 4. Content Management > Changeset History; note that default environment is locker 5. Click "Dev" in the Environment path UI element, observing the correct promotion of your TestChangeset 6. Click Locker in the Environnment path UI element. Actual results: Locker never changes color User cannot click through locker Expected results: User should be able to nav to Locker just like any other env. Additional info: Note: workaround is to simply do Content Management > Changeset History again, but that's still disjointed. User should be able to traverse the environment paths.