|
Project
|
YouTrack
|
|
Priority
|
Normal |
|
Type
|
Feature |
|
State
|
Submitted |
|
Assignee
|
Evgeniy Schepotiev |
|
Subsystem
|
Workflow |
|
Fix versions
|
Backlog |
|
Fixed in builds
|
No Fixed in build
|
|
Affected versions
|
No Affected versions |
|
Browser
|
Any Browser |
|
OS
|
Any OS |
|
Verified in build
|
Not verified
|
|
Verified by
|
Nobody |
|
Affected builds
|
No affected builds
|
|
Reviewed by
|
No reviewed by |
|
Story points
|
Undefined |
|
Value
|
|
|
Marketing value
|
No marketing value |
The first thing I want is exactly what the title for this issue says: introduce a separate role to reopen issues that is afaik not available right now.
Then, anything that would force a user to set forth a compelling reason before reopening an issue would work.
For example, this could be a workflow rule that requires commenting an issue on transition from a resolved state to Reopened.
Another thing to consider is preventing batch-reopening issues for security (and sanity) reasons. That is, no one should be allowed to select multiple resolved issues, and reopen them with a single comment. Reopening each issue should require a separate, unique comment.