Re: Anyone using UNCONFIRMED in Bugzilla?

[Tristan Van Berkom <tvb gnome org>]

I personally don't need a 'new' bug state.

However, I did run into a situation where old bugs were getting inadvertently
closed because they were 'unconfirmed', at which point I had to run through
my emails and re-open perfectly valid 'unconfirmed' bugs.

Again, I don't care if there are many bug states, add some if you wish,
I only need unconfirmed and resolved personally. I'll be happy that
at least bugs don't get inadvertently closed due to their long-term
'unconfirmed'ness.

Cheers,
            -Tristan

On Wed, Dec 28, 2011 at 3:24 AM, Dan Winship <danw gnome org> wrote:
> On 12/27/2011 10:43 AM, Matthew Barnes wrote:
>> I'd like to see UNCONFIRMED removed but maybe as a compromise add a "confirmed" Bugzilla keyword for projects to use or not use as they please.
>
> Stock bugzilla allows you to set on a per-product basis whether
> newly-created bugs are NEW or UNCONFIRMED, but as far as I was able to
> tell when I was looking at this
> (https://bugzilla.gnome.org/show_bug.cgi?id=658470) we explicitly
> removed that functionality on bgo.
>
> -- Dan
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list