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 359885 - duplicates.cgi: also displays resolved bugs with no resolution set
duplicates.cgi: also displays resolved bugs with no resolution set
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: bug data
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-05 13:48 UTC by André Klapper
Modified: 2009-08-21 06:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description André Klapper 2006-10-05 13:48:19 UTC 
dear bugzilla masters,

even when i set duplicates.cgi to display only open bugs, like http://bugzilla.gnome.org/duplicates.cgi?sortby=count&reverse=1&maxrows=75&changedsince=60&openonly=1
i still get bugs that are resolved, but do not have a resolution field entry, like bug 94514.

current code says
        # We want to show bugs which:
        # a) Aren't CLOSED; and
        # b)  i) Aren't VERIFIED; OR
        #    ii) Were resolved INVALID/WONTFIX
i think we also don't want to show bugs with
bug_status=resolved && resolution=NULL (or something like that, anyone with some perl knowledge will know so much better than i do).

thanks in advance...
Comment 1 André Klapper 2006-10-05 14:05:14 UTC 
by the way, i'd also love to get the NEEDINFO bugs displayed in that list, and the product instead of the component, and the status instead of the Op Sys.

feel free to slap me. ;-)
Comment 2 Olav Vitters 2006-10-11 09:49:12 UTC 
A bug should not have an empty resolution. Changing this would just hide the database corruption.
Comment 3 André Klapper 2006-10-18 00:05:17 UTC 
bkor, so this a bug data issue.
(i consider your comment as a confirmation.)
if so, how many bugs are affected? perhaps this is not a high priority. :-/
Comment 4 Max Kanat-Alexander 2009-08-21 06:33:20 UTC 
I fixed this by handling bugs that had a missing resolution.