show whether an Incomplete bug task can expire, and why

Bug #737008 reported by Alex Rousskov on 2011-03-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

Bug #319140 has been marked as incomplete for ecap project since 2009-02-09, but it is not counted as incomplete in "Incomplete bugs (can expire)" counter and does not expire. I also marked the same bug as incomplete for squid project today but that did not change the counter so I assume it will still not expire as it should.

I am not sure, but the problem may be related to the fact that the bug report was filed before the project was configured to expire incomplete bug reports.

Curtis Hovey (sinzui) wrote :

The ecap task cannot expire because it is assigned...someone acknowledges it is an issue and is working on it. The second task may also be blocking expiration. See
    https://help.launchpad.net/BugExpiry

Changed in launchpad:
status: New → Invalid
Alex Rousskov (rousskov) wrote :

Silently not expiring assigned incomplete bugs feels wrong because, in general, whether there is a person assigned to handle a bug report has nothing to do with that bug report completeness, but I appreciate pointing me to the documentation about bug expiration criteria. Thank you.

I wonder if we should show some text saying "this old incomplete bug
won't expire because it's assigned", though perhaps that's kludgy.

Martin

Robert Collins (lifeless) wrote :

I think a self documenting UI is a good idea - I'm sure we could do a
tasteful expiry-status thing somewhere on the bug, which when moused
over shows 'cannot expire: expiry disabled for project foo', 'cannot
expire: task is in progress', 'will expire in 4 days' etc.

You already show "This bug report will be marked for expiration in 59 days if no further activity occurs. (find out why)" message above the incomplete bug report. If that code is enhanced to explain why the incomplete bug is not marked for expiration, it would help avoid confusion and invalid bug reports such as mine. A mouse over would also work, I guess, but it is less obvious and does not reuse the existing approach/code.

Martin Pool (mbp) wrote :

I'm not sure if a mouseover in particular is best (not so discoverable or scannable; you can't click it for help), but something along the lines of Robert's comment would be good.

Changed in launchpad:
status: Invalid → Triaged
importance: Undecided → Low
summary: - old incomplete bugs are not treated as incomplete
+ show whether an Incomplete bug task can expire, and why
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers