Feature #11943
openNew project setting to disallow issue editing unless a valid state transition is allowed
0%
Description
There should be new project setting that disallows issue editing unless a valid state transition is allowed for the specific role, tracker, and state. This is much less costly than the hassle of editing field permissions like crazy to get the same effect.
I currently have just under 5000 workflow permissions created just to create a more restrictive editing process. This was a serious hassle to create, and the number would be significantly reduced, and speed would be increased, if this feature were implemented.
A new -> new transition would allow someone to edit a new issue. An in progress -> in progress transition would allow someone to edit an issue in progress. A closed -> closed transition would allow someone to edit a closed issue.... and so on.
As mentioned above, a new project setting (that defaults to 'off') maintains backwards compatibility.
Updated by Brian Lindahl about 12 years ago
Note that this would also require that the role had the 'edit issue' permission.
Updated by Brian Lindahl about 12 years ago
Also, not having the default transition (new -> new) would disallow the creation of the tracker. This would allow for disabling tracker creation on a per-role basis. In other words, the tracker would not appear in the drop-down list.