Deny editing of descriptions of closed issues
When a project is marked as "closed" I think it'd be a reasonable default to deny editing the description.
As there's no history for the description this would allow opening editing to restriced roles until the task is finished - while denying it afterwards.
#3 Updated by Ве Fio almost 9 years ago
Interesting. Our typical workflow is to assign the issue beforehand and start ("In Progress") it later.
Thus #7444 "edit the issue until the issue has been assigned." won't be applicable.
The main use case would be:
Deny lower priviledged users to change history.
The desriptions of maybe long past issues would be preserved in the state they were when "Closed".
#6 Updated by Brian Lindahl almost 9 years ago
Ahh, I misread. Probably due to the confusion in that once an issue is assigned, we consider the workflow to be started (at least someone besides the author has taken note of the issue). Rather than your team, where it appears that you consider the workflow to be started once someone is actively working on it (In Progress).