Bug 14772 – "Preset Queries: My Bugs" query is too restrictive

• Product: Gentoo Infrastructure
• Status: RESOLVED INVALID

[Description D Wollmann 2003-01-30 05:09:05 UTC]

The "My Bugs" query limits its results to bugs that are marked NEW, ASSIGNED, or
REOPENED. If a bug's status is changed to RESOLVED, it drops off the bug filer's
radar. It's a mistake to assume that most filers will bother trying to find a
bug if it doesn't show up in this query's result set (unless the bug is a real
show-stopper) and, given bugzilla's less-than-user-friendly UI, it's not a
certainty that the majority of those who bother to try to find a bug that's gone
missing from "My Bugs" will find it.

Since most users who file bugs expect to be able to find them with this query no
matter what their current state is, the query should include no "bug_status"
parameters. Marking a bug RESOLVED doesn't necessarily mean that the bug is
fixed, it only indicates that the assignee is satisfied that it's fixed on the
configurations available to him for testing. The filer's configuration may say
otherwise, and he should be given the opportunity to confirm or dispute the
assignee's assertion that the bug has been resolved.

All of a user's bugs should be included in the result set if possible. Bugs
who's state has changed to RESOLVED should most certainly be included in this
query, this is probably the most important bug state.

The current query:

http://bugs.gentoo.org/buglist.cgi?
bug_status=NEW
&bug_status=ASSIGNED
&bug_status=REOPENED
&email1=converter%40dalnet-perl.org
&emailtype1=exact
&emailassigned_to1=1
&emailreporter1=1

Removing the "bug_status" parameters returns all bugs filed by the user.

[Comment 1 John Davis (zhen) (RETIRED) 2003-01-30 14:53:33 UTC]

This does seem like a decent idea, but it has one major flaw -
We have some developers with *a ton* of bugs, and alot of them are resolved. Including this in the query would create a ton of bloat and unnecessary load on the server.