More precise "Edit issue" permission
|Category:||Permissions and roles|
The problem :
Most of the time you want testers (or any other significant role) in your project team to be able to change the ticket status to "validate", "feedback" or "reject" a ticket after testing.
Currently you can allow a "tester" role to "Edit Issue", allowing testers to do the required change.
But it provide too much powers to testers that are not developers/managers! With this permission the testers can also change the initial description of the ticket!
For some projects you might also want to not allow "developers" to change the initial description of a ticket, only let them add comments to it and allow only admin or "managers" to change it.
Still developers need to be able to change the ticket status, even if not allowed to edit the whole ticket description.
The feature would :
- add a new permission "Edit Ticket Status" that would then allow the user to change the status;
- make the permission "Edit Issue" allow status AND description permission edition;
An alternative (but more expensive?) solution would be to specify witch fields of a ticket can be modified when the "Edit Issue" permission is on, for each role where it's on. That would allow even more precision in permission management.
#3 Updated by Go MAEDA over 2 years ago
- Category changed from Issues permissions to Permissions and roles
- Status changed from New to Closed
- Resolution set to Duplicate
You can set fields to read-only for particular roles and statuses with "Fields permissions" in the workflow page. This feature was implemented in Redmine 2.1.0 (#3521).