Feature #3521

Permissions for roles to change fields per tracker/status

Added by Robert Gonzalez about 8 years ago. Updated almost 5 years ago.

Status:ClosedStart date:2009-06-22
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Permissions and roles
Target version:2.1.0
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.

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


Related issues

Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only ... Closed 2011-04-03
Related to Redmine - Feature #10697: Split role permission for "edit ticket" Closed
Related to Redmine - Feature #13814: No more comments when ticket closed New
Duplicated by Redmine - Feature #5067: Read only custom field Closed 2010-03-13
Duplicated by Redmine - Feature #1919: Separate permissions for changing assigned-to, % finished... Closed 2008-09-18
Duplicated by Redmine - Feature #8134: Restrict edit issue possibilities per role Closed 2011-04-12
Duplicated by Redmine - Feature #7557: Deny editing of descriptions of closed issues Closed 2011-02-05
Duplicated by Redmine - Feature #583: Make "Assign To" field read only or disabled for certain ... Closed
Duplicated by Redmine - Feature #10394: Implement permission "Assign users to issues". Closed
Duplicated by Redmine - Feature #10950: need help add issue without any selection Closed
Duplicated by Redmine - Feature #10684: hide list of assignees when creating new issue Closed

Associated revisions

Revision 9977
Added by Jean-Philippe Lang about 5 years ago

Workflow enhancement: editable and required fields configurable by role, tracker and status (#703, #3521).

Revision 9979
Added by Jean-Philippe Lang about 5 years ago

Removed hard-coded strings (#703, #3521).

Revision 9980
Added by Jean-Philippe Lang about 5 years ago

Fills locales (#703, #3521).

Revision 9985
Added by Jean-Philippe Lang about 5 years ago

ruby1.8 compatibility (#703, #3521).

History

#1 Updated by Daniel Jones almost 8 years ago

+1

#2 Updated by Greg Mefford over 7 years ago

+1

#3 Updated by minkbear minkbear over 7 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

#4 Updated by Terence Mill over 5 years ago

related to #8050

#5 Updated by Jean-Philippe Lang about 5 years ago

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

#6 Updated by Hannes Meier about 5 years ago

is also closing ticket #10697

#7 Updated by Michał Chełmiński about 5 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.

#8 Updated by Gabriel Mazetto almost 5 years ago

#11887 may be a bug related with this feature

#9 Updated by Go MAEDA over 2 years ago

  • Duplicated by Feature #10394: Implement permission "Assign users to issues". added

#10 Updated by Go MAEDA over 1 year ago

  • Duplicated by Feature #10950: need help add issue without any selection added

#11 Updated by Go MAEDA 12 months ago

  • Duplicated by Feature #10684: hide list of assignees when creating new issue added

Also available in: Atom PDF