Bug 1042901 - Menu hierarchy/directions for custom content providers is incorrect
Summary: Menu hierarchy/directions for custom content providers is incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs User Guide
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Megan Lewis
QA Contact: Athene Chan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 15:32 UTC by Walden Raines
Modified: 2019-09-25 20:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 14:05:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Walden Raines 2013-12-13 15:32:27 UTC
Description of problem:

The menu item hierarchy here  is incorrect:  

https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/chap-Content_Management.html#sect-Using_Custom_Content_Providers

It should read: Content -> Repositories -> Products

After arriving on the products page you create a custom product and a custom provider from the new product page.  Afterwards you can add repositories to the created product.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2013-12-13 15:56:20 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Megan Lewis 2014-03-13 23:26:34 UTC
Hi Walden, 

Thanks for the feedback. We'll correct the menu hierarchy. The changes will be in the documentation of the next release. 

Thanks and have a great day, 
Megan

Comment 8 Athene Chan 2014-06-20 04:45:56 UTC
Verified.

Comment 9 Bryan Kearney 2014-07-02 14:05:09 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.


Note You need to log in before you can comment on or make changes to this bug.