Description of problem: The Component list of the guided bug entry form for RHEL 6 (possibly other versions as well) is missing the entry for the Component Description "RHEV Hypervisor Deployment Guide" which is causing all trailing Component Descriptions to be offset by one, beginning with the current next Component list element of "doc-Installation_Guide". Thus, the Component Description for "doc-Installation_Guide" is "RHEV Hypervisor Deployment Guide" whereas it should have the Component Description of "Installation Guide" which is attached to the next Component list element; this behavior continues for the remainder of all Component Descriptions. Version-Release number of selected component (if applicable): Noticed under RHEL 6 guided bug entry for bz 4.4 How reproducible: Very Steps to Reproduce: 1.Create New Bug for RHEL 6 using guided bug entry form. 2.Under Step 2, in the Component listbox, select "doc-Installation_Guide" 3.Note Component Description of missing previous element "RHEV Hypervisor Deployment Guide" Actual results: All Component Descriptions are offset by one beginning with the Component Description "doc-Installation-Guide" and continuing for the remainder of all Component Descriptions. Expected results: Component Descriptions match Component list elements. Additional info:
Guided bug entry form for RHEL 6 URL: https://bugzilla.redhat.com/enter_bug.cgi?format=guided&product=Red%20Hat%20Enterprise%20Linux%206
The code that generates the list of component descriptions was also including inactive components, however the code that generates the select list itself /was not/ including inactive components. This is what was causing the off by one error. I've put in the check, and also modified the template to put the distribution component at the head of the list. ( see bug 576320 ) The upstream guided template page has this check from version 4.4 onwards. This fixes the problem with the description not matching the component name.
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.