Bug 1244286

Summary: [RFE] Confusing in finding Layered Red Hat repositories to sync in UI under Content->Red Hat Repositories
Product: Red Hat Satellite Reporter: Dave Sullivan <dsulliva>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, bkearney, cwelton, rjerrido, tpapaioa
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-12 13:13:29 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 Dave Sullivan 2015-07-17 16:25:51 UTC 
Description of problem:

I went back in forth looking at my manifest which should have provided a subscription to cover software collections but didn't see Software Collections under Content--->Red Hat Repositories--->RPMs

Found out they were under the "Other" tab this is not very intuitive

I would probably do the following:

Change RPMs tab name to Core RPMs

I'd move the "Other" tab to the right of "Core RPMs" tab and I would call it "Addon RPMs"

On the "Core RPMs" tab page I would have a note at the top that mentions Addon RPMs, maybe a link"

Note: See Addon RPMs tab for layered red hat repositories (e.g. Software Collections)




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

6.1
Comment 2 Brad Buckingham 2016-06-16 15:34:54 UTC 
*** Bug 1344778 has been marked as a duplicate of this bug. ***
Comment 3 Brad Buckingham 2016-06-16 15:36:00 UTC 
When implementing a solution for this bug, please review and consider any duplicate bugs that may be associated with it.  E.g. bug 1344778.
Comment 4 Bryan Kearney 2017-10-12 13:13:29 UTC 

*** This bug has been marked as a duplicate of bug 1455322 ***