Bug 789148

Summary: RFE: Customizable BZ Information
Product: [Community] PressGang CCMS Reporter: Misha H. Ali <mhusnain>
Component: Web-UIAssignee: Matthew Casperson <mcaspers>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 1.xCC: cbredesen, jwulf, topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-17 04:41:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Deadline: 2012-03-15   

Description Misha H. Ali 2012-02-09 23:11:17 UTC 
Description of problem:

All documentation generated by Skynet current has the hard coded EAP BZ information implicitly included. This should be part of the filter to be configurable per product.

FYI, the BZ information traditionally defined in the Book_Name.ent file via publican are as follows:

<!ENTITY BZURL "http://bugzilla.redhat.com">
<!ENTITY BZPRODUCT "JBoss Enterprise Data Grid 6">
<!ENTITY BZCOMPONENT "Documentation">
Comment 1 Misha H. Ali 2012-02-09 23:21:50 UTC 
Correction, jwulf has pointed out that the filters and the Build Docbook tab fields in Skynet are independent of each other. In this case, what I meant to say was that the inclusion of the provided BZ information under the Build Docbook tag would seem to be sufficient.
Comment 2 Joshua Wulf 2012-02-10 00:01:44 UTC 
The search filters are saved sets of search criteria.

The "Build Docbook" dialog has a bunch of parameters for building Docbook output.

THe Bugzilla component for a given Docbook output build would be a parameter of the "Build Docbook" dialog.

Are the Build Docbook parameters currently saved as part of the search filter?

If not, should they be? Or should they be saved as their own "Docbook outputs"?

I can see at least one use case where you might want to decouple them - a testing version and a production version of the same topics - so the search filter is the same, but the Build Docbook parameters are distinct. That could be dealt with by saving the search filter twice with different names and different Build Docbook parameters, or by making the saved search filter and the saved Build Docbook parameters two different entities.
Comment 3 Matthew Casperson 2012-02-17 00:15:14 UTC 
Fixed in final 20120217-0922

The files that are prepopulated in the bugzilla link are now exposed under the "Build DOcbook" tab.