Redmine

Similar feature implemented in patch #7444:
subjects/descriptions are denied editing once the issue has been assigned (once the workflow has begun)

Note that this patch also implements other issue permissions.

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".

How can an issue be 'In Progress' without someone working on it (assigned to someone)? I can't see how that makes sense.

Brian Lindahl wrote:

I can't see how that makes sense.

It doesn't ;)

As stated we first assign the issue and set it to "In Progress" later.

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).