countdown expiration with multiple entries

[dino99]

Seems that bug reports which have multiple entries (affects also projects):

 like bug # 849414, when they are marked as "incomplete", the countdown expiration always stay on 59 days expiration (dont start counting down)

like bug #553745, when only some projects are marked as "incomplete", the countdown expiration dont start (the warning sentence dont appear on top of bug report also) for these projects (seems its fail to start on partial 'incomplete' entries)

[Julian Edwards (julian-edwards)]

This is not a bug, please see https://help.launchpad.net/BugExpiry

[dino99 (9d9)]

Well a countdown saying expirying in 59 days, days after days after weeks, i'm calling such a broken countdown, e.g. a bug. The link above dont refer to such cases reported above or abandonned project(s) even if it says "In a future Launchpad release".

[Jeroen T. Vermeulen (jtv)]

On bug 849414 at least, there is a good reason why the counter stays at 59 days: there have been regular comments on the bug, and each of those resets the counter. So for this example at least, the counter is behaving correctly and as documented: “the last update was more than 60 days ago.”

So arguably, maybe, we shouldn't show the counter for a few days, as long as people are still updating the bug. But there's a problem with that: we need to be sure that people _see_ that there is a counter! When there are no updates, we have no guarantee that this will be noticed.

Then again, maybe there is something else going on that this example does not show. Do you see any other examples, where the counter is at 59 days but there have been no updates for more than a day?

I'll mark this bug as Incomplete for now; if you do find an example where the counter is clearly wrong, please post it here and we can change the status.

[Martin Pool (mbp)]

> So arguably, maybe, we shouldn't show the counter for a few days, as long as people are still updating the bug.

I think dino99 has a point that this seems a bit odd, and perhaps we shouldn't do that.

> But there's a problem with that: we need to be sure that people _see_ that there is a counter! When there are no updates, we have no guarantee that this will be noticed.

Why do we _need_ to do this? Does the counter motivate people to respond to the bug more quickly? If they have any information to add, probably they will already add it without the counter to remind them. And if the bug does expire incorrectly, that's easily fixed.

[Gavin Panella (allenap)]

The countdown could be shown only when there's only 50% (for example) remaining, so 30 days or less.

[Martin Pool (mbp)]

On 14 October 2011 21:08, Gavin Panella <email address hidden> wrote:
> The countdown could be shown only when there's only 50% (for example)
> remaining, so 30 days or less.

+1

[dino99 (9d9)]

Hello maintainers,

any progress on that side ?