Hide Forgot
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">
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.
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.
Fixed in final 20120217-0922 The files that are prepopulated in the bugzilla link are now exposed under the "Build DOcbook" tab.