After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658470 - please kill the UNCONFIRMED state
please kill the UNCONFIRMED state
Status: RESOLVED DUPLICATE of bug 744312
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: Bugzilla 4.4
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-07 14:06 UTC by Dan Winship
Modified: 2015-02-27 15:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Winship 2011-09-07 14:06:01 UTC 
Almost no maintainers on bgo reliably make a distinction between UNCONFIRMED and NEW. This leads to users complaining about bugs that are "still" marked unconfirmed even after lots of users "me too" them, etc. (eg, https://bugzilla.gnome.org/buglist.cgi?chfieldto=Now;query_format=advanced;chfieldfrom=2011-08-01;longdesc=UNCONFIRMED;longdesc_type=casesubstring. There are a handful of false positives in there, but note that that's just bugs modified in the last month). 

This also leads to confusion when reopening bugs, because it seems completely non-intuitive to change the bug from RESOLVED to UNCONFIRMED, and occasionally people get confused and change it to VERIFIED instead.

From googling around, it looks like in our version of bugzilla, UNCONFIRMED only exists if voting is enabled, which is weird since I would have said voting wasn't enabled on bgo... It also looks like maybe you can disable it on a per product basis by changing the "votes to confirm" parameter on the product to "0", but I don't seem to be able to change that on the products I administer...
Comment 1 Dan Winship 2011-10-12 14:15:24 UTC 
(In reply to comment #0)
> From googling around, it looks like in our version of bugzilla, UNCONFIRMED
> only exists if voting is enabled, which is weird since I would have said voting
> wasn't enabled on bgo... It also looks like maybe you can disable it on a per
> product basis by changing the "votes to confirm" parameter on the product to
> "0", but I don't seem to be able to change that on the products I administer...

It looks like in the bugzilla-newer module, the upstream NEW-vs-UNCONFIRMED behavior was ripped out, and it just hardcodes NEW for maintainers, UNCONFIRMED for everyone else.

But I think that's not really the version of bugzilla that's running on bgo? Where is the current bgo source/config?
Comment 2 Olav Vitters 2011-12-28 09:06:42 UTC 
Bugzilla source is at: https://launchpad.net/bugzilla.gnome.org

We need to upgrade to have the "use unconfirmed" checkbox. Seems very useful.
Comment 3 Olav Vitters 2012-01-03 10:12:29 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 4 Allison Karlitskaya (desrt) 2012-08-23 13:21:51 UTC 
Any word on when this will be deployed?
Comment 5 André Klapper 2015-02-27 15:04:37 UTC 
(In reply to Ryan Lortie (desrt) from comment #4)
> Any word on when this will be deployed?

Next week.

*** This bug has been marked as a duplicate of bug 744312 ***