Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Allow components to have different default descriptions|
|Product:||[Community] Bugzilla||Reporter:||Alexander Todorov <atodorov>|
|Component:||Creating/Changing Bugs||Assignee:||Simon Green <sgreen>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||tools-bugs <tools-bugs>|
|Version:||3.6||CC:||asn, dmach, ebaak, jingwang, jlaska, jmorgan, kbaker, sbose|
|Fixed In Version:||4.4-3||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-05-20 07:03:30 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||460257|
Description Alexander Todorov 2008-08-27 02:57:30 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. Additional info: As I was told such functionality doesn't exist in Bugzilla ATM, see bug #460257.
Comment 1 Noura El hawary 2008-12-01 23:59:02 EST
Hi Alexander, 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. Noura
Comment 2 Alexander Todorov 2008-12-02 03:20:16 EST
Hi Noura, 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 <> Description: <add component foo to RHEL. This is the request to include foo in comps.xml> Packages to be added: <foo, foo-devel> Comps group: <foo is in development-tools, foo-devel is in development-libs> Default: <no> Mandatory: <no> Visible: <yes> Multi-lib: <no> Need to be present for arches: <i386, x86_64>
Comment 3 David Lawrence 2008-12-02 11:45:41 EST
Comment 4 Alexander Todorov 2008-12-03 02:35:02 EST
AJAX + filtering by product sounds best.
Comment 5 David Lawrence 2010-01-15 12:32:02 EST
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.
Comment 6 David Lawrence 2010-08-25 17:39:56 EDT
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. Thanks Bugzilla Development Team
Comment 7 Alexander Todorov 2010-09-03 12:08:53 EDT
This is still relevant.
Comment 8 Simon Green 2011-08-18 01:55:52 EDT
*** Bug 706369 has been marked as a duplicate of this bug. ***
Comment 9 Simon Green 2012-06-19 02:15:25 EDT
Comment 10 Alexander Todorov 2012-06-19 04:02:32 EDT
Comment 11 Simon Green 2012-10-10 23:43:10 EDT
(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?
Comment 12 Alexander Todorov 2012-10-11 03:18:53 EDT
(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