Re: Killing off UNCONFIRMED in Bugzilla



Then how will project devs know if a bug is - as the status implies - not yet confirmed? It may be a problem with a single users unique setup, or a design decision, or caused by something specific to a certain distribution... Isn't that the point of this tag?

On February 13, 2015 4:51:58 PM CET, Olav Vitters <olav vitters nl> wrote:
With Bugzilla 4.4 we can disable UNCONFIRMED on a per-product basis.
With that option available, I suggest to kill off the UNCONFIRMED status
for all products except whomever wants it. I think we had this
discussion before, but couldn't easily find that.

Reasoning to kill unconfirmed:
Unconfirmed at various times gives the impression the bug will not be
looked at. Not having this state would solve that.

Action required:
IF YOU WANT TO KEEP UNCONFIRMED FOR YOUR PRODUCT PLEASE SPEAK UP!!


Steps (for all products except the ones opting out):
- Change "use unconfirmed" to false (product specific setting)
- Mass change all unconfirmed bugs to new for all

Timeline:
I want to do this Friday 27 February 2015.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]