Project

General

Profile

Actions

Feature #1919

closed

Separate permissions for changing assigned-to, % finished and target version

Added by Finn Gruwier Larsen over 15 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Permissions and roles
Target version:
-
Start date:
2008-09-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

Currently, access to these fields is controlled through the status workflow permissions. It would be better if they had there own permissions in order to get more fine-grained control over user permissions. My actual problem is that I want to create a "customer" role that should be able to make some status transitions (f. ex. open > closed), but customers should not be able to change assigned-to, % finished and target version.


Related issues

Related to Redmine - Feature #703: Configurable required fields per tracker/status/roleClosedJean-Philippe Lang2008-02-21

Actions
Related to Redmine - Feature #1360: Permission for adding an issue to a version.Closed2008-06-03

Actions
Related to Redmine - Feature #9421: Prevent attribute changes once an issue is assigned to a closed versionClosed2011-10-13

Actions
Has duplicate Redmine - Defect #7729: User with only issue view and add note ermission can change issue statusClosed2011-02-26

Actions
Is duplicate of Redmine - Feature #3521: Permissions for roles to change fields per tracker/statusClosedJean-Philippe Lang2009-06-22

Actions
Actions

Also available in: Atom PDF