Opinions about possible new workflow in b.x.o

[Auke Kok]

On 03/19/2011 05:46 AM, Jérôme Guelfucci wrote:
> On 17/03/11 22:53, Nick Schermer wrote:
>> Bugzilla 4.0 has a new status workflow
>> (http://www.bugzilla.org/releases/4.0/release-notes.html#v40_feat_workflow):
>>
>>
>> - UNCONFIRMED (default when bug is created)
>> - CONFIRMED
>> - IN_PROGRESS
>> - RESOLVED
>> - VERIFIED
>>
>> Currently we use this flow:
>>
>> - NEW
>> - ASSIGNED
>> - REOPENED
>> - RESOLVED
>> - VERIFIED
>> - CLOSED
>>
>> Once b.x.o is updated to bugzilla 4 (will probably happen with 4.0.1)
>> we can choose to switch to the new flow or keep the old one.
>> Personally I agree with the ideas behind this new work flow, so I
>> wouldn't mind switching, but others might feel different about that.
>>
>> Nick
>
> Hi Nick,
>
> First thanks you for raising this and taking care of our bugzilla setup!
>
> I'm ok with the new workflow, it's pretty much the same as before. The
> only thing I miss is an INCOMPLETE state, which allows a more
> fine-grained triaging.
>
> UNCONFIRMED -> CONFIRMED if we have everything we need
> UNCONFIRMED -> INCOMPLETE if we need more details, backtrace, test case...

use NEEDINFO for that - it's a bit more clear what is needed, and it 
works well for several bugzillas I work with.

Auke