Automatic bug expirations
Bug #35344 reported by
James Blackwell
This bug report is a duplicate of:
Bug #91925: Automatically expire old unassigned Incomplete bug reports.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I would love it if I could do one of two things:
1. Have "need info" bugs automatically close if there are no comments for 30 days.
2. Have a checkbox that would close a bug in 30 days if the status is not changed to confirmed.
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
Revision history for this message
| Diogo Matsubara (matsubara) wrote | #2 |
| Changed in malone: | |
| importance: | Medium → Wishlist |
| status: | Unconfirmed → Confirmed |
To post a comment you must log in.
I certainly sympathize with the need to not have half-complete bugs cluttering up the system.
Automatically closing them might be a bit drastic for some projects.
An alternative (though more complex) is:
* implement the other bug that asks for sorting by last activity
* do a query for needinfo bugs sorted by least recent activity
* walk through and review/close/ping the user/see if they're already fixed/etc