Bug 1255745

Summary: RFE: Create buttons to switch between host and content host pages
Product: Red Hat Satellite Reporter: Fred van Zwieten <fvzwieten>
Component: HostsAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-18 19:59:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fred van Zwieten 2015-08-21 12:39:05 UTC 
Description of problem:
Create a button on the "host" page that will jump to the content host of this specific host (if present)
Create a button on the "content host" page that will jump to the host of this specific host (if present)

The button should be greyed out it the object to jump to doesn't exist.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
This is a great way to navigate between these two related objects, without having to go through various screen to get to the related object. Also the ling waiting time for procucing the content host list as a intermediate step is very annoying in this process.
Comment 1 Brad Buckingham 2015-11-18 19:59:27 UTC 
Today, there are cross links between hosts and content hosts.

E.g. 
All Hosts -> Host -> click host : from here, should be able to click Content or the Subscription status, if there is an associated content host

All Hosts -> Content Hosts -> click content host -> Provisioning tab : from here, should be able to click on link, if there is an associated host

This behavior could be more prominent and improved.  That said, in 6.2 the team is working on backend changes to unify the 2 models (host & content host) and then in 6.3, the goal is to also unify the UI as well.