Bug 1051952

Summary: RFE: Product Name for Content Specs List
Product: [Community] PressGang CCMS Reporter: Misha H. Ali <mhusnain>
Component: Web-UIAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3CC: lnewson, mcaspers
Target Milestone: ---   
Target Release: 1.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-23 23:43:57 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:
Bug Depends On:    
Bug Blocks: 1037269    

Description Misha H. Ali 2014-01-13 00:40:22 UTC 
In the render view, the "Render fir Content Spec" drop down menu would be more useful if it contained a product name as well as the book name. I can't get a screenshot but for a topic I am currently looking at (ID 8849), the list contains six "Administration and Configuration Guide" items. This information would make more sense with a product name since information that is usually included in one type of guide (Admin Guide) would likely be in the same type of guide for other products.

For context, I use this drop down menu to see whether the topic is used in any other product's documentation before thinking about changes.
Comment 1 Lee Newson 2014-02-14 21:44:56 UTC 
For your specific case you should probably be using the "Content Specs" tab, as that was what it was designed for.

As for the RFE, this is more than likely going to cause the dropdown to contain too much data to the point where you'd need a 1920x1080 displays to be able to read the additional information anyways. As such we possibly need a way to group the Content Specs in the list by product instead, or maybe have another dropdown where you select the product first. Anyways we'll need to look into this more closely when we take a look at implementing this RFE.
Comment 2 Lee Newson 2014-02-14 21:51:31 UTC 
As an additional note, as to why this shouldn't be used for checking if the topic is used by other product's documentation, is that the list only shows content specs that have entities or conditions defined. Any other content specs are all grouped under the "DEFAULT" option.
Comment 3 Lee Newson 2014-02-15 08:18:12 UTC 
I ended up requiring having to do this anyway for BZ#1037269.

Added in 1.4-SNAPSHOT build 201402151749

The content spec list is now grouped together into product/version to help identify what content spec you are rendering the topic for. The groups are also sorted alphabetically to make it easier to find your topics.

Note: This version is currently deployed on the development/test server.