[Bugsquad] Custom fields for bugzilla
Michael Leupold
lemma at confuego.org
Mon Sep 15 15:14:10 CEST 2008
Hi,
I did a writeup of all the stuff we might like to have in bugzilla and wanted
some feedback.
Something that's about to come anyways:
* NEEDSINFO - this could be a flag but I think dirk already has plans to
implement that workflow-enabled
Existing fields we need enabled:
* enable useqacontact - This will give us an extra QA Contact field we can put
the bugsquad assignee into. This assignee will receive mails as if he was CCed
to the bug.
New fields:
* cf_bugsquad_on - date-field. if set this shows that and when the bug was
triaged.
* cf_bugsquad_reproduce - selection box. Yes/No - if we could reproduce the
bug
* cf_bugsquad_resolution - multiple-selection box. These are our proposed
resolutions. The values are the same as the standard ones, WORKSFORME, FIXED,
... + WISH (for making it a wish)
* cf_bugsquad_special_need - text-field describing special needs this bug has
(special server software, special locale, ...)
* cf_bugsquad_duplicate - text-field. If we think a bug is a duplicate we can
enter the possible duplicate here as well as the cause why we think it's a
duplicate.
-> The cause for setting the fields (especially cf_bugsquad_resolution) has to
be entered into the comment field - so that stays basically the same like we
do now.
* new FLAGS:
* bs_developer - bugs needing special attention
* bs_high-profile - high profile bugs
* bs_delayed - if the bug couldn't be checked due to NEEDSINFO or
cf_bugsquad_special_need
Version field policy:
The version field policy should be the same for all applications we triage. I
propose setting the last version this bug could be reproduced. This will help
developers backporting fixes and also tell us which bugs we could re-triage if
a new version is released.
No longer needed in my opinion:
"no longer in 4.x". We'll be able to tell that from the version and
cf_bugsquad_resolution/reproduce.
Policy for double checking:
As all the flags and fields we introduce are searchable we'll be able to look
for bugs that have a cf_bugsquad_resolution set but aren't RESOLVED yet. Like
this it's easy to find bugs that should be double-checked before they are
closed.
A problem that will need to be solved:
If all operation takes place in bugzilla we'll either have to give new
triagers full permission to get them started, have them record their findings
externally or give them a subset of the permissions so they can access all the
fields they need for triage (and give them full permissions like we do now).
Please post your ideas. I want to get this to the sysadmins as soon as it's
agreen upon.
Regards,
Michael
More information about the Bugsquad
mailing list