There should be a report to show "Needs Info bugs that have had a response"

Bug #50663 reported by Brad Bollenbach
22
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Eleanor Berger

Bug Description

There should be a report to show "Needs Info bugs that have had a response"

Tags: lp-bugs motu
Brad Bollenbach (bradb)
Changed in malone:
status: Unconfirmed → Confirmed
Revision history for this message
Christian Reis (kiko) wrote :

Well, either that, or the reporter commenting on a bug should move the status back to whatever it was before, don't you think?

Revision history for this message
Carthik Sharma (carthik) wrote :

Reverting the status back to whatever it was before may be suboptimal. A report that shows needs info bugs that have had a response would be more useful that just reverting the status back.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Bughelper should cover even fairly complicated versions of this -- like Need Info bugs where the second to last comment is by me. (eventually)

https://wiki.ubuntu.com/BugHelper

Revision history for this message
Matthew Lange (matthewlange) wrote :

I think to be more specific, it should be a search for bugs that have been commented on since it was set to "needs info". (This comment is basically common sense, but emphasis on "since", since most any "needs info" bug will have a comment.)

Revision history for this message
Christian Reis (kiko) wrote :

Once we have the new statuses in place it will be a good thing to handle the Needs Info (Incomplete) workflow better by making it easy to move back, and/or expiring items which stay for too long in that status.

Changed in malone:
assignee: nobody → intellectronica
Revision history for this message
Eleanor Berger (intellectronica) wrote :

Had a pre-imp call with ~jtv and I think this is the solution:

- Needs info is now called Incomplete.
- Add a new search option to BugTaskSearchListingView in the group of status checkboxes - "Incomplete (with response)" and rename the existing incomplete checkbox to "Incomplete (without response)" (or maybe we can come up with better names).
- in BugTaskSet.searchTasks add the new option and change the behavior of the old incomplete option so that they are mutually exclusive (otherwise choosing both renders the search meaningless).
- Extend the search query to look for bugs which are in incomplete status, where the last change to the status (in bugactiviry) is earlier than the last bugmessage.
- This can be tested both by pagetests and by testing the database objects directly in doctests.

Changed in malone:
status: Confirmed → In Progress
Revision history for this message
Eleanor Berger (intellectronica) wrote :

Complete and reviewed, but hasn't landed on time for 1.1.8

Changed in malone:
status: In Progress → Fix Committed
Changed in malone:
status: Fix Committed → Fix Released
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.