Bug 86010 - Default query doesn't include RESOLVED bugs
Default query doesn't include RESOLVED bugs
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: PnT DevOps Devs
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-03-12 04:20 EST by Reuben Thomas
Modified: 2013-06-23 23:10 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-04 16:34:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Reuben Thomas 2003-03-12 04:20:04 EST
Description of problem:

Yesterday I submitted three bug reports against RH8.0. All of them turned out to be duplicates, so I wasted my time (bother!) and yours (sorry!). I had queried all three packages to check first. What did I do wrong? I used the default query, which doesn't include RESOLVED bugs, and hence had overlooked the fact that the bugs I was after had already been fixed.

Now I know, I've added RESOLVED to my default query. But I'm guessing there are lots of others out there who will make the same mistake, and was wondering if it made sense to change the "default default" to include RESOLVED bugs. The average user reporting bugs will want to check the bug they are about to report isn't already resolved, won't they?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 David Lawrence 2006-04-08 13:54:50 EDT
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Comment 2 David Lawrence 2008-09-16 12:49:54 EDT
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Note You need to log in before you can comment on or make changes to this bug.