Project

General

Profile

Actions
Copy link

Feature #3521

closed

Permissions for roles to change fields per tracker/status

Added by Robert Gonzalez almost 15 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jean-Philippe Lang
Category:
Permissions and roles
Target version:
2.1.0
Start date:
2009-06-22
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

It would be nice to have (possibly in the same page as the workflow administration) a toggle for a role for a tracker so that updating a field is allowed or disallowed. I.e. since RedMine is already allowing or disallowing the change of the status in the work flow from some previous state to some new state, why not make a simple addition that extends this to any field, but not for every possible state change of those fields, just a simple gating switch of whether or not a change is allowed for that role.

For example, I do not wish developers to be able to move a bug to another version. Right now there is no way to disallow this basically. This should be the function of a manager, who makes the decision together with the stakeholders of whether or not a feature/bug, etc. is moved to a future version.

Files

workflow_permissions.png (13.7 KB) workflow_permissions.png Jean-Philippe Lang, 2012-07-15 18:24

Related issues

Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory Closed2011-04-03

Actions
Related to Redmine - Feature #10697: Split role permission for "edit ticket"Closed

Actions
Related to Redmine - Feature #13814: No more comments when ticket closedNew

Actions
Related to Redmine - Feature #10922: Allow tracker only for SubtaskClosed

Actions
Related to Redmine - Feature #1445: add new permission 'edit issue planning'Closed2008-06-13

Actions
Related to Redmine - Feature #13422: "Edit assigned user" permission for issuesClosed

Actions
Has duplicate Redmine - Feature #5067: Read only custom fieldClosed2010-03-13

Actions
Has duplicate Redmine - Feature #1919: Separate permissions for changing assigned-to, % finished and target versionClosed2008-09-18

Actions
Has duplicate Redmine - Feature #8134: Restrict edit issue possibilities per roleClosed2011-04-12

Actions
Has duplicate Redmine - Feature #7557: Deny editing of descriptions of closed issuesClosed2011-02-05

Actions
Has duplicate Redmine - Feature #583: Make "Assign To" field read only or disabled for certain roles.Closed

Actions
Has duplicate Redmine - Feature #10394: Implement permission "Assign users to issues".Closed

Actions
Has duplicate Redmine - Feature #10950: need help add issue without any selectionClosed

Actions
Has duplicate Redmine - Feature #10684: hide list of assignees when creating new issueClosed

Actions
Has duplicate Redmine - Feature #5239: privilege to assign an issueClosed2010-04-02

Actions
Has duplicate Redmine - Feature #6036: user permission is changing as the workflow state is changedClosed2010-08-05

Actions
Has duplicate Redmine - Feature #6219: More precise "Edit issue" permissionClosed2010-08-26

Actions
Has duplicate Redmine - Feature #4684: Allow for customizable view permissions when adding an issueClosed2010-01-28

Actions
Has duplicate Redmine - Feature #4485: Create an ACL privilege for assigning ticketsClosed2009-12-25

Actions
Actions
Copy link

Also available in: Atom PDF