Re: [Bugzilla] Missing option to go from WAITING to UNCONFIRMED?

[Daniel Berlin <dberlin at dberlin dot org>]

On Friday, July 11, 2003, at 1:07 AM, Nathanael Nerode wrote:

> Dan Berlin thought:
> > In the unconfirmed state (ie the bug was never confirmed prior to
> > being in WAITING), there is no need for a transition because it's 
> > *already*
> > unconfirmed. Thus, the only reasonable transition is to NEW or
> > RESOLVED/<something like INVALID>.
>
> One use case for a WAITING->UNCONFIRMED transition is this, I think:
> the feedback was received but we're still trying to decide whether it's
> really a bug or not.  This can take a while in some of the C++ cases.  
> :-)  I
> suppose we can just leave the bugs in NEW state then, but it's not as
> informative.

Why not leave them in WAITING?  It means it's undecided still, it's 
just not waiting on feedback from a user, it's waiting on feedback from 
a developer. If it's a real bug, you eventually mark it NEW, if it's 
not, you eventually resolve it as invalid anyway.

I *can* allow a WAITING->UNCONFIRMED transition for non-everconfirmed 
bugs, but this would then mean you couldn't use WAITING->UNCONFIRMED if 
you closed and reopened the bug (one would hope this  situation would 
never happen. Even i can't imagine such a f*cked up case that would 
make you want to do that).

I just can't allow WAITING->UNCONFIRMED for everconfirmed bugs.

The fact that some WAITING bugs would be able to become UNCONFIRMED, 
and some wouldn't (IE the button wouldn't appear) might confuse the 
hell out of someone not familiar with the whole issue, which is why i 
just left it alone.

If we really want it, i'll throw it on my todo list (which consists of 
2 bugzilla tasks right now, and about 4 non-bugzilla ones)