Feature #1919

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

Added by Finn Gruwier Larsen about 9 years ago. Updated over 5 years ago.

Status:ClosedStart date:2008-09-18
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Permissions and roles
Target version:-
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/role Closed 2008-02-21
Related to Redmine - Feature #1360: Permission for adding an issue to a version. Closed 2008-06-03
Related to Redmine - Feature #9421: Prevent attribute changes once an issue is assigned to a ... Closed 2011-10-13
Duplicated by Redmine - Defect #7729: User with only issue view and add note ermission can chan... Closed 2011-02-26
Duplicates Redmine - Feature #3521: Permissions for roles to change fields per tracker/status Closed 2009-06-22

History

#1 Updated by Mike D. Smith over 8 years ago

+1
I would very much like to restrict the same fields for a reporter role.

#2 Updated by Paulo Aguiar about 8 years ago

+1
Another one interested in such a feature

#3 Updated by Tomáš Řihošek over 7 years ago

+1
would be useful for custom fields too.

#4 Updated by Tomáš Řihošek over 7 years ago

  • % Done changed from 0 to 90

see ;)

#5 Updated by Tomáš Řihošek over 7 years ago

  • % Done changed from 90 to 0

#6 Updated by Nicole Dumfart about 7 years ago

++
I think it should be possible to restrict every field to the roles.
Also custom fields...

#7 Updated by Mischa The Evil about 7 years ago

Added relation to issue #703 (and thus its related issues).

#8 Updated by Toggi Muppet about 7 years ago

This is a "must have"....

#9 Updated by Assis Calazans about 7 years ago

I have the same problem related by Gruwier. My costumers have an area to add tickets in a especific workflow.
Still waiting for this feature.

#10 Updated by Etienne Massip over 6 years ago

  • Target version set to Candidate for next major release

#11 Updated by Albert M over 6 years ago

+1

#12 Updated by Giovani Spagnolo over 6 years ago

+1
we also use "customer/partner" roles and something we'd like to do is to hide "estimated time" and "time spent" fields from them.
it could be somehow configurable which fields (including custom fields) are visible by roles.

#13 Updated by Terence Mill over 6 years ago

covered by #8050

#14 Updated by Justin Mayer almost 6 years ago

This issue is very narrowly-focused and discrete, which I think makes it a great candidate for near-term implementation. Judging by the number of related (and still open) issues, plus the number of comments posted to those issues, the demand for this functionality is overwhelmingly large:

  • #703: refers to required fields, which isn't really related to permissions
  • #3090: duplicate
  • #5011: duplicate
  • #5037: makes reference to custom fields, which is larger in scope than limits placed on built-in fields
  • #8050: would address this issue, but is much larger in scope

As a product manager, I'm a big fan of prioritizing small, discrete features that can have a big impact, and this issue certainly seems to fit that description. Please consider this my strident vote for incorporating this feature in the next release.

#15 Updated by Александр Закревский over 5 years ago

+100500
Much insterested in! My Customers/Reporters must not have the right to assign or reassign issues as this misleads my side developers. In my situation only project managers have the authority to do that. Used side plugin to handle the situation, but it blocks major version updates due to incompatibility.

#16 Updated by Christopher Proud over 5 years ago

+1

#17 Updated by Eric Strennen over 5 years ago

+1000

#18 Updated by Eric Strennen over 5 years ago

BTW, I deployed the Field Permissions plugin by Romain Silva and it addresses most of this issue. Per role, you can enable/disable access to Assignee, Target Version, Estimated Time and Due Date. Definitely a step in the right direction.

#19 Updated by Александр Закревский over 5 years ago

Eric Strennen wrote:

BTW, I deployed the Field Permissions plugin by Romain Silva and it addresses most of this issue. Per role, you can enable/disable access to Assignee, Target Version, Estimated Time and Due Date. Definitely a step in the right direction.

Me too, but it worked only for 1.3.x. After upgrade to 1.4.x I faced troubles running this plugin, so I had to roll back.

#20 Updated by Jean-Philippe Lang over 5 years ago

  • Status changed from New to Closed
  • Target version deleted (Candidate for next major release)
  • Resolution set to Duplicate

Implemented as part of #3521 for 2.1.0.

Also available in: Atom PDF