GNOME Bugzilla – Bug 138046
clarify meaning of unconfirmed->NEW and make easier for 'experts'
Last modified: 2018-06-16 13:28:38 UTC
Find edit_bug template, find all places where you have an option to make a bug NEW, and put a little (ie font -1) warning in saying "Please only confirm the bug if you have followed the bug triage guidelines and checked for duplicates."
Necessary if we want to use new 'right', so marking high priority so we don't forget about it.
This is not pretty, but it's there. Hopefully we can reconsider the whole unconfirmed->new bit at some point- maybe 'new' becomes 'triaged'?
cvs -z3 diff -u -r 1.9 -r 1.8 template/en/default/bug/create/create.html.tmpl Andrew points out this patch that allows people with bits to skip unconfirmed and go directly to new. Also, retitling to turn this into a bit of a meta-bug. I'm not comfortable with the current state of things- we've tried to turn NEW into TRIAGED without really making that explicit, and we're trying to sort of merge REPLICATED and TRIAGED. I think it's probably better than what was, but still not great.
I think currently we rather prefer to kill UNCONFIRMED and only use NEW. See bug 658470
Also see my comments in bug 740076 about this
*** Bug 740076 has been marked as a duplicate of this bug. ***
UNCONFIRMED will get mostly killed in bug 744312. After that, not sure if we still want to change something here and how.
After https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure , GNOME is moving its task tracking from Bugzilla to GitLab at https://gitlab.gnome.org/ as previously announced in https://mail.gnome.org/archives/desktop-devel-list/2018-May/msg00026.html . See https://wiki.gnome.org/GitLab for more information. Hence closing this ticket as WONTFIX: There are no plans to work on Bugzilla.