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:
Given an id, if you need a specific URL to access the details of a Provider/System/Organization/Environment/Role/User/Changeset in UI, we cannot do it in Katello at this point. For example if we need to access the details of a system with id=111, we cannot user http://<FQDN>/katello/systems/111 , since that just renders the raw html. Similarly http://<FQDN>/katello/systems#panel=system_111 may not if the system 111 is not in the 25 system limit window. The only way to do this at the present time is to http://<FQDN>/katello/systems?search=id%3D111#panel=system_111 .
This basically does a
"go to systems list; look for system with id 111; show that"
so on the left there is only one system and that is automatically chosen.
Two issues with this approach:
1) That "id = 111" shows up in the filter box. This may or may not be acceptable
2) 'id' on scoped search has been only implemented on system for now, but not on others. We may or may not want to go with this approach.
Given the restful nature of the application, attempting to solve this through use of search parameters seems convoluted. I propose adding the ability to restfully select a single item and have it display as the lone item in the list on a normal 2pane page. For example, /systems/11/ would show the normal systems page with only system 11 in the left hand list with the details page popped out.