Project

General

Profile

Actions

Feature #8570

closed

Extension of the tracker-role relation

Added by St├ęphane David about 13 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
Issues permissions
Target version:
-
Start date:
2011-06-09
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

At the moment, it is possible to define for each role and each type of tracker the workflow. This is nice, but present a big problem for me : it's not possible to restrict the visibility of some type of trackers to some role.

I would very much appreciate an extension of this function, to define, for each role and each tracker, if the role can
1) See the tracker. This is the most important. I'd like that at least, when going to a project, a role cannot see at all the issues related to a specific tracker (exemple of use : the users can see the "user reported issues" tracker, but not the "internal issues" tracker).

only for the tracker he is allowed to use
2) Create new issues
3) See own issues
4) See other issues
5) Edit own issues
6) Edit other issues

At the moment, if if a role can do nothing with a type of tracker (every status in the worklow are disabled), he can still see the issues for this tracker, even if he can't change the status.


Related issues

Related to Redmine - Feature #285: Tracker role-based permissioningClosedJean-Philippe Lang

Actions
Actions #1

Updated by Jean-Baptiste Barth about 13 years ago

  • Priority changed from High to Low

As you said, it may be a problem for you. Such privacy options could be interesting but not for the vast majority of Redmine audience. Maybe you could propose a (tested) patch to implement the behavior you propose ? I can't promess it will be integrated. An even better option would be to implement that in a plugin.

Actions #2

Updated by Go MAEDA about 5 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Redmine 3.3.0 and later support role-based access control for trackers (#285).

Actions

Also available in: Atom PDF