Project

General

Profile

Actions

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
Category:
Permissions and roles
Target version:
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 #1

Updated by Daniel Jones over 14 years ago

+1

Actions #2

Updated by Greg Mefford about 14 years ago

+1

Actions #3

Updated by minkbear minkbear about 14 years ago

+1

very agree with this feature but...
try to take a look at link below.

#5032
#4670
#703
#1091
#4927
#4684
#4309
#3090

Actions #4

Updated by Terence Mill about 12 years ago

related to #8050

Actions #5

Updated by Jean-Philippe Lang almost 12 years ago

  • File workflow_permissions.png workflow_permissions.png added
  • Subject changed from Add on/off permissions for roles to change fields in a tracker to Permissions for roles to change fields per tracker/status
  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.1.0
  • Resolution set to Fixed

Feature added. You can now configure read-only fields per tracker, status and role.

A new tab is added to the workflow settings to configure read-only standard/custom fields. This same form is used to configure required fields as well (#703):

Note that if a user has multiple roles on the same project, only fields that are read-only for all its roles are actually read-only.

Actions #6

Updated by Hannes Meier almost 12 years ago

is also closing ticket #10697

Actions #7

Updated by Michał Chełmiński almost 12 years ago

I have a question. I want to implement these Feature #3521 in redmine 2.0.1. but it will work ?

This feature will be very useful in my company. I have no time to wait 45 days for new version 2.1.0. On monday I am starting a new project and I need this feature.

Actions #8

Updated by Gabriel Mazetto over 11 years ago

#11887 may be a bug related with this feature

Actions #9

Updated by Go MAEDA over 9 years ago

  • Has duplicate Feature #10394: Implement permission "Assign users to issues". added
Actions #10

Updated by Go MAEDA about 8 years ago

  • Has duplicate Feature #10950: need help add issue without any selection added
Actions #11

Updated by Go MAEDA over 7 years ago

  • Has duplicate Feature #10684: hide list of assignees when creating new issue added
Actions #12

Updated by Go MAEDA over 6 years ago

Actions #13

Updated by Go MAEDA about 6 years ago

  • Has duplicate Feature #5239: privilege to assign an issue added
Actions #14

Updated by Go MAEDA about 6 years ago

  • Has duplicate Feature #6036: user permission is changing as the workflow state is changed added
Actions #15

Updated by Go MAEDA almost 5 years ago

  • Has duplicate Feature #6219: More precise "Edit issue" permission added
Actions #16

Updated by Go MAEDA over 4 years ago

  • Has duplicate Feature #4684: Allow for customizable view permissions when adding an issue added
Actions #17

Updated by Go MAEDA over 4 years ago

  • Related to Feature #1445: add new permission 'edit issue planning' added
Actions #18

Updated by Go MAEDA almost 3 years ago

  • Related to Feature #13422: "Edit assigned user" permission for issues added
Actions #19

Updated by Holger Just 3 months ago

  • Has duplicate Feature #4485: Create an ACL privilege for assigning tickets added
Actions

Also available in: Atom PDF