Bug 226150 - "Show all open reports I ..." does not include NEEDSINFO (which is still useful for the bug reporter)
Summary: "Show all open reports I ..." does not include NEEDSINFO (which is still usef...
Status: RESOLVED FIXED
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR normal
Target Milestone: ---
Assignee: Matt Rogers
URL:
Keywords:
: 270799 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-10 16:05 UTC by jamundso
Modified: 2022-08-05 00:25 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jamundso 2010-02-10 16:05:05 UTC
Version:            (using KDE 4.4.0)
Installed from:    I Don't Know

Really, "Show all open..." should include everything *except* CLOSED.
For example, my link for "Show all open reports I reported" is
https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailreporter1=1&emailtype1=exact&email1=jamundso%40gmail.com

Likewise with the "CC'd" and "commented" reports.
Based on the life cycle at https://bugs.kde.org/page.cgi?id=fields.html, the NEEDSINFO, RESOLVED, and VERIFIED statuses should be included.
Thank you.
Comment 1 Dario Andres 2010-02-10 16:19:28 UTC
Mh, https://bugs.kde.org/page.cgi?id=fields.html should be updated.
We don't use "CLOSED" nor "VERIFIED" in this bugtracker because we don't have that much time nor manpower to re-check the issues.
"RESOLVED" is usually *the "closed" state* (RESOLVED/FIXED, RESOLVED/DUPLICATE, RESOLVED/*STREAM)

NEEDSINFO is a special (temporary) state; which could be discussed.

IMHO, RESOLVED and VERIFIED should *not* be included in the "open reports" queries, as they are not "open" in our workflow.

Regards
Comment 2 jamundso 2010-02-10 17:51:26 UTC
(In reply to comment #1)
> Mh, https://bugs.kde.org/page.cgi?id=fields.html should be updated.
> We don't use "CLOSED" nor "VERIFIED" in this bugtracker because we don't have
> that much time nor manpower to re-check the issues.
> "RESOLVED" is usually *the "closed" state* (RESOLVED/FIXED, RESOLVED/DUPLICATE,
> RESOLVED/*STREAM)

Sounds reasonable, and thanks for that. Pursuant to this, I request that :
1. The 253 bugs currently in the VERIFIED state be changed to RESOLVED.
2. The status choices "CLOSED" and "VERIFIED" be removed as options, and the above page updated.
3. Somebody re-send the "workflow" memo to all Assigned To accounts.

> NEEDSINFO is a special (temporary) state; which could be discussed.

Fair enough. Here's my part of the discussion. :-)
In some ways, this bug system is already unfriendly to Reporter's - we cannot do anything with bugs we did not report except to add comments or vote. For our own bugs, we can only comment, vote, or change to RESOLVED or NEEDSINFO status.

Unless I'm missing something, the "Show all open reports..." are key to the Reporter's use of this site. Except for the e-mail notification, they are the easiest way to find the things we work on, and yet changing a bug to NEEDSINFO excludes it from those reports. I fail to see the benefit of that. Note, this is not meant as criticism, just giving my perspective. 
thanks, again.
Comment 3 Dario Andres 2010-02-10 19:42:49 UTC
Mh, usually the bug reporter doesn't have to handle the report status (or other fields) him/herself...

But I have missed an important point on this... as the links is mostly intended for bug reports to check which own reports are still open and could be still value, and sometimes you need to provide more info on a NEEDSINFO value (and that is the reason a bug report is "closed" as NEEDSINFO) then it would be a good idea to include this state on a "open reports" query

Other option would be "show all the report I sent" ... 

Updating title. Regards
Comment 4 Christoph Feck 2011-04-13 01:25:19 UTC
*** Bug 270799 has been marked as a duplicate of this bug. ***
Comment 5 Gunter Ohrner 2011-04-13 21:32:35 UTC
Sorry for the duplicate, I somehow missed this report. :-(

As I already wrote in Bug 270799, I think it's *especially* important for NEEDSINFO bugs to be as visible to the reporter as possible.

Contrary to a normal NEW/UNCONFIRMED/ASSIGNED bug, which will or won't be fixed no matter if the reporter monitors it, a NEEDSINFO requires the reporter to take action before it can be resolved.

From my point of view, such bugs actually should be listed as a welcome page right after every login...
Comment 6 Tom Albers 2012-12-19 19:16:12 UTC
NEEDSINFO added to the query. Thanks for reporting.