Red Hat Bugzilla – Bug 460258
Allow components to have different default descriptions
Last modified: 2014-10-12 18:45:51 EDT
Description of problem:
QA and rel-eng teams have agreed to start using a predefined template when filing comps bugs. This will improve work of both teams as all the necessary information will be provided in comment #0.
As I was told such functionality doesn't exist in Bugzilla ATM, see bug #460257.
so looking at this bug and bug #460257 now this bug seems to be more specific to as it is specifying a component that needs a default template in the description field of the bug entry form. Can you please provide more description on what you need to be implemented, like the steps to get to the comps template and what would the template look like.
bug #460257 is a generic issue request. If no particular text is specified for a component use the current one.
For the comps case: the standard template is not helpful since comps is different and QE needs different information in the bug report. We think having all of this into a template and values filed in the first comment will significantly speed up handling of comps bugs. Here's a possible template, values are enclosed in <>
<add component foo to RHEL. This is the request to include foo in comps.xml>
Packages to be added:
<foo is in development-tools, foo-devel is in development-libs>
Need to be present for arches:
One problem we have is we don't know which component is selected at page render time so we would need to do one of two things.
2. Use AJAX to pull the proper text from the server when a component is selected.
Number 1 would be fine if we only have a few components with custom texts, but if we have 100's or even 1000's then the page becomes too large and will degrade UI performance.
Number 2 would be better as the initial page load would be small and we would only pull the text we need from the server. We would need to load a initial data structure that had a true/false value per component so that the AJAX call would not be made if a component does not have a custom text.
We would also need to filter this based on product as well as other products may not want this behaviour.
AJAX + filtering by product sounds best.
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this feature will need to be implemented against the new release.
Updating bug version to 3.2.
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.
Bugzilla Development Team
This is still relevant.
*** Bug 706369 has been marked as a duplicate of this bug. ***
(In reply to comment #9)
> won't see this.
> Additionally, if the user has already made a change to the
> comment box and they then change the component that has a different default
> text, do we wipe out their changes or not change the box?
Don't wipe out the text but instead append new text at the bottom. How does this sound?
(In reply to comment #0)
> Description of problem:
> QA and rel-eng teams have agreed to start using a predefined template when
> filing comps bugs. This will improve work of both teams as all the necessary
> information will be provided in comment #0.
What do you mean by comps bugs?
(In reply to comment #11)
> (In reply to comment #0)
> > Description of problem:
> > QA and rel-eng teams have agreed to start using a predefined template when
> > filing comps bugs. This will improve work of both teams as all the necessary
> > information will be provided in comment #0.
> What do you mean by comps bugs?
Bugs against comps/rel-eng components