Project

General

Profile

Actions

Feature #3521

closed

Permissions for roles to change fields per tracker/status

Feature #3521: Permissions for roles to change fields per tracker/status

Added by Robert Gonzalez over 17 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Category:
Permissions and roles
Target version:
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 19 (1 open — 18 closed)

Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory ClosedActions
Related to Redmine - Feature #10697: Split role permission for "edit ticket"ClosedActions
Related to Redmine - Feature #13814: No more comments when ticket closedNewActions
Related to Redmine - Feature #10922: Allow tracker only for SubtaskClosedActions
Related to Redmine - Feature #1445: add new permission 'edit issue planning'ClosedActions
Related to Redmine - Feature #13422: "Edit assigned user" permission for issuesClosedActions
Has duplicate Redmine - Feature #5067: Read only custom fieldClosedActions
Has duplicate Redmine - Feature #1919: Separate permissions for changing assigned-to, % finished and target versionClosedActions
Has duplicate Redmine - Feature #8134: Restrict edit issue possibilities per roleClosedActions
Has duplicate Redmine - Feature #7557: Deny editing of descriptions of closed issuesClosedActions
Has duplicate Redmine - Feature #583: Make "Assign To" field read only or disabled for certain roles.ClosedActions
Has duplicate Redmine - Feature #10394: Implement permission "Assign users to issues".ClosedActions
Has duplicate Redmine - Feature #10950: need help add issue without any selectionClosedActions
Has duplicate Redmine - Feature #10684: hide list of assignees when creating new issueClosedActions
Has duplicate Redmine - Feature #5239: privilege to assign an issueClosedActions
Has duplicate Redmine - Feature #6036: user permission is changing as the workflow state is changedClosedActions
Has duplicate Redmine - Feature #6219: More precise "Edit issue" permissionClosedActions
Has duplicate Redmine - Feature #4684: Allow for customizable view permissions when adding an issueClosedActions
Has duplicate Redmine - Feature #4485: Create an ACL privilege for assigning ticketsClosedActions

Updated by Daniel Jones about 17 years ago Actions #1

+1

Updated by Greg Mefford over 16 years ago Actions #2

+1

Updated by minkbear minkbear over 16 years ago Actions #3

+1

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

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

Updated by Terence Mill over 14 years ago Actions #4

related to #8050

Updated by Jean-Philippe Lang over 14 years ago Actions #5

  • 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.

Updated by Hannes Meier over 14 years ago Actions #6

is also closing ticket #10697

Updated by Michał Chełmiński over 14 years ago Actions #7

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.

Updated by Gabriel Mazetto about 14 years ago Actions #8

#11887 may be a bug related with this feature

Updated by Go MAEDA almost 12 years ago Actions #9

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

Updated by Go MAEDA over 10 years ago Actions #10

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

Updated by Go MAEDA about 10 years ago Actions #11

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

Updated by Go MAEDA almost 9 years ago Actions #12

Updated by Go MAEDA over 8 years ago Actions #13

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

Updated by Go MAEDA over 8 years ago Actions #14

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

Updated by Go MAEDA over 7 years ago Actions #15

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

Updated by Go MAEDA almost 7 years ago Actions #16

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

Updated by Go MAEDA almost 7 years ago Actions #17

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

Updated by Go MAEDA over 5 years ago Actions #18

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

Updated by Holger Just over 2 years ago Actions #19

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

Also available in: PDF Atom