[Koha-devel] Patch status workflow (for Bugzilla)

[Paul Poulain]

Le 25/10/2011 17:17, Ian Walls a écrit :
> Community,
> 
> 
> As I'd mentioned in a previous thread, I think we should consider
> removing the custom attribute "patch status" from Bugzilla, and keeping
> track of this information in the regular Status attribute.  This has
> several advantages:
> 
>   * Easier searching, since it's a default value, not a custom value
>   * We can enable Workflows between Statuses
>   * We no longer have the dependency on Priority to control the display
>     of this critical value
> 
> The Workflows allow us to specify how tickets are allowed to change
> status, from which to which.  Here's an example workflow:
> 
>   * NEW (default for all incoming tickets)
>   * ASSIGNED (to the developer working on it)
>   * NEEDS_SIGNOFF (once a patch has been submitted)
>   * SIGNED_OFF (after signoff)
>   * PASSED_QA (once QA'ed successfully)
>   * PATCH_PUSHED
>   * RESOLVED

other potential problem : when moving all existing bugs/patches to those
new status,
 we will set the "last modification date" to "today" right ?
can't it be the source of some
glitch/pain/problem/surprise/misunderstanding ?
(just asking)


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