Re: Killing off UNCONFIRMED in Bugzilla

[Andre Klapper <ak-47 gmx net>]

On Sat, 2015-02-14 at 19:02 +0100, Sébastien Wilmet wrote:
> On Fri, Feb 13, 2015 at 06:43:35PM +0100, Sébastien Wilmet wrote:
> > For example in gedit UNCONFIRMED means that the bug is not triaged.

How and to who does it actually matter?
If it currently means that no developer will take a look at those
tickets (though some of them might be totally valid) and if no other
triagers are around, wouldn't it make sense to get rid of UNCONF so
developers might suddenly & accidentially look at such tickets? ;)

> What about NEW and CONFIRMED statuses?

I am reluctant to rename statuses; see my other email.

> Or is it possible to search bugs that haven't been touched by any
> developer of that product?

Currently not possible as far as I know:
Bugzilla's "Custom Search" at the bottom of "Advanced Search" allows
"Commenter | is not equal to | %group.setproductnamehere_developers%"
but that criterion is already true when at least one commenter (e.g.
reporter) is not member of the developers group for that product.

Relatedly, https://bugzilla.gnome.org/page.cgi?id=browse.html now offers
a "Bugs without a response" link again in the sidebar. 
But that is a lie as it only offers tickets with exactly one comment.
Still better than nothing I thought, as long as upstream does not fix
https://bugzilla.mozilla.org/show_bug.cgi?id=704842 ...

Cheers,
andre
-- 
Andre Klapper  |  ak-47 gmx net
http://blogs.gnome.org/aklapper/