| 1 |
On 3/7/11 11:13 AM, Brian Harring wrote: |
| 2 |
> Re-read what he stated- it'll convert all existing NEW bugs to |
| 3 |
> CONFIRMED upon migration. There's a fair number of bugs that are in a |
| 4 |
> NEW state, decent number that have sat for a long while too. Those |
| 5 |
> bugs aren't 'confirmed'- just like with the new work flow where the |
| 6 |
> dev flips it from UNCONFIRMED to CONFIRMED, leave it to devs to flip |
| 7 |
> the current bugs from UNCONFIRMED to CONFIRMED rather than just |
| 8 |
> marking everything as CONFIRMED. |
| 9 |
|
| 10 |
Maybe I'm misunderstanding something, but it seems we have both |
| 11 |
UNCONFIRMED and NEW in the "old" workflow. My understanding is that |
| 12 |
CONFIRMED is the new name for NEW, which makes sense. |
Archives