[Koha-devel] Proposal to change Bugzilla Status and Patch Status values

[Paul Poulain]

Le 06/01/2012 15:37, Ian Walls a écrit :
> Fellow Koha-ckers,
> I'd like to remove Patch Status, and move all those values to the
> regular Status field.  This has the following advantages:
> 
>   * Status is a built-in field, so it's got much richer support in
>     Bugzilla.  For example, status workflows can be added.  Patch Status
>     is a custom field, and is just a list of values
>   * We would no longer lose the Priority value of a bug by having to set
>     it to Patch Sent in order to get the Patch Status values visible
>   * Statuses can be updated as part of submitting an attachment like a
>     patch, streamlining the patch submission process (fewer clicks to
>     keep all the fields up to date).
+1000, that's a change I really want to have !

> I'd also like to add a new status, "In Discussion", for bug reports that
> have deeper procedural, philsophical or technical implications outside
> that of mere coding (bug 7167 being an example).

> We're not using Status for anything else, so there is no trade-off
> there.  This is really how the Status field is meant to be used.  We
> will, however, have to rebuild the canned searches that look for patches
> that Need Signoff, are Signed Off, and are Passed QA/Failed QA.
rewriting the canned searches is not a big deal ! and the positive thing
is so great !
> 
> The other difficulty of this proposal is that we'll need to turn off
> automatic bug emails for a bit while we make the bulk changes to the
> Patch Statuses; otherwise, we'll all get spammed to high heaven with
> meaningless updates when the migration occurs.

easy : bugzilla > Administration > Parameters > Email >
mail_delivery_method set to none

not really a difficulty, we must just warn ppl !

> What do people think?  Does this sound like a reasonable change to
> make?  Any objections?
it's a desirable new year gift, definetly !

(another reason to do that = if you close a bug that has an needs
signoff because, for example, it's invalid, or a duplicate patch exists,
then it will still appear in the needs signoff list, because the patch
status has nothing to see with the bug status. That's weird)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08