[Bugzilla] Missing options to go from WAITING to UNCONFIRMED?

[Andrew Pinski]

One of the current problems is that all the bugs that were converted 
from GNATS in the
waiting state were marked as being confirmed so one bug I tried to 
switch from WAITING
to UNCONFIRMED but since it was marked as being ever confirmed, 
bugzilla got it wrong
(PR 11100).  I had to turn it back to waiting because I could not 
extract the files
when there were cated to together.

Thanks,
Andrew Pinski

On Friday, Jul 11, 2003, at 01:18 US/Eastern, Daniel Berlin wrote:
> On Friday, July 11, 2003, at 1:03 AM, Nathanael Nerode wrote:
>
>> Dan Berlin said:
>>> In the confirmed state (Ie the bug was confirmed prior to being in
>>> WAITING), you run into the same problems you would trying to 
>>> transition
>>> from NEW to UNCONFIRMED. It's not as simple as changing the status, 
>>> and
>>> doesn't make sense anyway.
>>
>> Unfortunately, it *does* make sense.  We've had "misconfirmed" bugs
>> before, which weren't really confirmed (although someone thought 
>> they's
>> confirmed it, they messed up).  I've being meaning to ask for a
>> NEW->UNCONFIRMED option for a while now, although it shouldn't be used
>> very often.
>
> I view it as a social problem, more than anything else.
> Don't go confirming bugs that shouldn't be confirmed. :)
> When in doubt, don't confirm.
> That said, allowing NEW->UNCONFIRMED would mess up a *whole* bunch of 
> things.
> There are things that look at the bug activity (history) to see if a 
> bug has been in a confirmed state or not, in addition to the 
> everconfirmed flag.
> I'd have to literally rewrite the bug activity history in order to 
> change NEW->UNCONFIRMED.
> This is a very bad thing.
>
>
>
>