Roundup Tracker - Issues

Issue 2550927

classification
Title: Prevent reopening of issues after some time period has passed.
Type: rfe Severity: minor
Components: User Interface Versions:
process
Status: new Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: rouilj
Priority: low Keywords:

Created on 2016-10-01 20:26 by rouilj, last changed 2016-10-01 20:42 by rouilj.

Messages
msg5907 Author: [hidden] (rouilj) Date: 2016-10-01 20:26
While updating issue2550926 I remembered I had been asked
about preventing an issue from being reopened after some
number of days.

The use case was that users were keeping old issues and replying to them
when they had some other (often unrelated) issue. This cluttered closed
issues in a few ways:

  stats for reopened issues were messed up.

  a confusing jumble of problems were merged on an issue

  since it's a reopen of an issue, the user may not get a
     confirmation email.

The suggestion was a user can reopen the issue within 14 days of it
being closed. Past that point the issue will not reopen.
If we implement this, the number of days/hours should be settable
as a config option.

The question is what needs to be done when the issue isn't reopened:

I claim the update should be rejected and a rejection email sent to
the author.

Accepting the email (and notifying people on the nosy list) but keeping
the status as resolved was also a use case.

Also creating a new issue (linking it back to the issue the user was
trying to update) was a third way to handle this.

So we have: create new, accept and reject as options at least.

Also none of this addresses the problem with the "thanks for your help"
message a few minutes after resolution causing the issue to reopen 8-(.

Other thoughts?
History
Date User Action Args
2016-10-01 20:42:28rouiljsettitle: Prevent reopening of issues after some time -> Prevent reopening of issues after some time period has passed.
2016-10-01 20:26:50rouiljcreate