[RFE] Malone should email, then close bugs for inactivity

Reported by Aaron Whitehouse on 2007-09-20
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned

Bug Description

Launchpad/Malone could automatically send a notice after a month saying "There has been no activity on your bug, is it still occurring?" and change the status to INCOMPLETE.

After a couple of warnings, Launchpad/Malone could automatically close the bug.

This seems to be what people are doing manually, anyway, but they are not always doing it consistently. Automating the process may move the focus of people from doing this to helping people avoid it. It would free up triager time to hold bug-reporters' hands through the debugging process.

Aaron Whitehouse (luna-tick) wrote :

This was just released!

Changed in malone:
status: New → Fix Released
Matthew Paul Thomas (mpt) wrote :

Actually, what was just implemented was changing long-inactive bug reports from Incomplete to Invalid, not setting them to Incomplete in the first place.

As for this particular request, I don't think it would be a good idea. I'm subscribed to dozens if not hundreds of valid bug reports that have been open for years. Having to actively keep them open every month would cause a lot of noise.

Yes... I think that you are right. Seeing how much traffic I received
from the long-invalid to incomplete change, I can appreciate the noise
this would create.

At the moment, though, it is entirely at random whether somebody
wanders past my bug, asks if it is still occurring and marks it as
incomplete. I feel that there should be a policy and that policy
should be automated.

Perhaps Bug #141202 would be a better way to deal with my concerns.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers