Red Hat Bugzilla – Bug 1228273
Subscription Details page is confusing in a multi-org context; should clear when switching between orgs
Last modified: 2016-07-27 04:52:25 EDT
Description of problem: When a user is viewing subscription details and then switches orgs, the subscriptions list on the left hand side changes accordingly, but the main view remains, showing details for the previously viewed subscription Version-Release number of selected component (if applicable): Compose 7 How reproducible: Steps to Reproduce: 1. Create two different orgs and import significantly different manifests into each. 2. While context is set to Org1, Go to Content > Red Hat Subscriptions 3. View details for one of the subscriptions ("x out of unlimited" or "x out of y", etc.) 4. While viewing subscription details, choose a different org from the context picker in the top left corner. 5. View results Actual results: The left pane changes correctly, properly showing the subscriptions for the selected Org. However, the Details window remains open, pointing to the previous subscription user was looking at before. Expected results: This is incredibly confusing; we shouldn't be seeing details irrelevant to an org after switching to it. Yes, there are workarounds -- simply hitting the close button on the Content Details, or by selecting a new subscription from the left pane. Regardless, this (the subscription details view) should probably be cleared/deselected when switching org contexts. Additional info:
Created redmine issue http://projects.theforeman.org/issues/14108 from this bug
PR: https://github.com/Katello/bastion/pull/100
Upstream bug component is Uncategorized
Moving to POST since upstream bug http://projects.theforeman.org/issues/14108 has been closed ------------- Walden Raines Applied in changeset commit:bastion|d02f043727370728e77c1d240a583e1759baef0a.
Verified in Satellite 6.2 Beta Snap 5.1. Context now shifts completely when switching orgs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1500