1 |
On Mon, Mar 07, 2011 at 08:24:46AM +0100, "Paweee Hajdan, Jr." wrote: |
2 |
> On 3/6/11 1:50 PM, Brian Harring wrote: |
3 |
> >> "NEW" will become "CONFIRMED" |
4 |
> > |
5 |
> > This seems mildly insane; sure you didn't mean UNCONFIRMED? |
6 |
> |
7 |
> I don't understand that concern. There is UNCONFIRMED and NEW, now you'd |
8 |
> get UNCONFIRMED and CONFIRMED. It seems to me it's just NEW with a |
9 |
> different name, and UNCONFIRMED would still be there: |
10 |
> |
11 |
> <http://bugzillaupdate.wordpress.com/2010/07/06/bugzilla-4-0-has-a-new-default-status-workflow/> |
12 |
|
13 |
Re-read what he stated- it'll convert all existing NEW bugs to |
14 |
CONFIRMED upon migration. There's a fair number of bugs that are in a |
15 |
NEW state, decent number that have sat for a long while too. Those |
16 |
bugs aren't 'confirmed'- just like with the new work flow where the |
17 |
dev flips it from UNCONFIRMED to CONFIRMED, leave it to devs to flip |
18 |
the current bugs from UNCONFIRMED to CONFIRMED rather than just |
19 |
marking everything as CONFIRMED. |
20 |
|
21 |
~harring |