Comment 9 for bug 196590

You can now use eg <https://bugs.edge.launchpad.net/bzr/+expirable-bugs> to see bugs in this state -- though I think there's no link to this page in the ui?

> if a reply is never looked at and the status updated, expiration is a good way of raising
> attention to it.

Maybe so. At present expiry only happens when it's the 'fault' of the reporter, rather than the developer. In practice at present this state means "if the reporter doesn't respond, we can't do anything else with this bug."

It would be interesting (perhaps extremely interesting ;-) to also expire bugs if they've had feedback from the user and the developer has not responded. You should presumably then also expire New bugs if the developer has not responded, because the situation is analogous, and it might even be logical to expire _all_ bugs if they're inactive for a long time, though that's probably taking it so far. It's useful to have old bugs still easily findable.

Expiry is quite aggressive in Answers and I think there it works reasonably well.

This would be less annoying in Bugs if it took the idea from answers of controlling state changes by single-click buttons next to the normal entry form. "Yes, this was the information we needed" vs "this bug is still incomplete".