Trackers per Role
|Category:||Permissions and roles|
I wonder if its possible to add a restriction per role , so a role only can see only the issues of a list of assigned trackers.
I propose this because, some of the trackers that we modeled are for internal usage and our should not see the information registered there.
I propose a list of features as showed in the permission reports but for the trackers. And then default behavios should be show all trackers
#2 Updated by Paul Macdonnell about 10 years ago
I would like to see this as well.
We have several Trackers and several Roles
I'd like it so only Technical roles can see issues in the Incident and Support Tracker.
Likewise the other roles can only see the Feature and Bug Trackers.
This is more than just being able to modify the status of an issue in a workflow (which is what you can currently do), this is allowing roles to see issues assigned to various Trackers or not.
The visibility table would look something like this then:
Tracker and issue visibility¶
If a role doesn't have permission to view a Tracker, they are unable to see any issues that have been assigned to that Tracker.
#4 Updated by Michael Sanders over 9 years ago
If you take a look at the originally written issue, I'm fairly certain that the actual request is to make it so that you define which Roles have which Trackers available for them to initially report issues on.
So, for instance, you would be able to control it so that the public can not put in a Task, as opposed to Suggesting a feature.
If that is the case, this issue is a duplicate of 2647
This is highly crucial and a basic-functionality request that is pivotal to my group's projects (we run 7 projects using Redmine.)
I highly recommend that an extra row is made in the Workflow menu of the Project Settings designated "Initial Creation" or something similar. This would be a mandatory field, that all projects have and cannot be deleted. The purpose would be to effectively describe "The user should have the permission to bring it from "Initial Creation" to "New" or whatever your Default Issue may be. Some people may see fit to allow people the access to submit to a tracker, only allowing a certain status for a specific role.
Obviously, if all of the checkboxes in Workflow were unchecked, someone of that Role would not be able to Create an issue.
#5 Updated by Chad Heuschober over 8 years ago
+1 one here.
We'd like to use a special tracker for our user stories so we can relate feature tracker issues back to their originating user stories, however, the user story owners are too nontechnical to be given free reign with the full issue tracker and have a hard time understanding how and where their requests go. Restricting them to just the one tracker would be best for us.
This issue has quite a few duplicates too. Please see:
#10 Updated by Stéphane David over 8 years ago
+1. At least make it so that some trackers can be set as not visible at all for a given role (cannot be created, and won't appear at all).
At the moment, it seems the only option is to create several subprojects with different trackers, but it's not really convenient
#18 Updated by Lázaro Hermoso almost 6 years ago
Definitely and improvement!
Maybe it could be implemented by adding more functionality in 'Issues visibility' within Roles and Permissions Administration Menu.
!Issues Visibility.JPG!When selecting a Role you can select Issues Visibility between:
- All issues
- All non private issues
- Issues created by or assigned to the user
- In my opinion a solution could be to add here the functionality of selecting the trackers that each role can view
In #8488 it was achieved to let watchers view issues eventhough their permission was set to 'issues created by or assigned to the user'. This is somehow a solution but it would be annoying to add users as watchers to every single issue.
I am sorry that I am not a developer and I cannot help with the code... :(
#21 Updated by Andy Puettmann over 5 years ago
There is sort of a workaround for this
I created a custom field type 'list' shown as 'checkbox' and made it required.
When assigning this field to only a single tracker 'project 3, bugs' I can have detailed 'create issue' permissions by making this field 'read-only' for all except the desired group.
(Field set to be visible only to 'permitted' groups)
This is not beautiful, but locks at least a few create issue and transition permissions.
#23 Updated by Alex Petty about 4 years ago
This is very much needed! (Does anyone have happen to have a 3.0.x compatible patch for this?)
Hopefully Jean-Phillipe Lang (and his core team) will recognize the importance of this feature and add it to Redmine's next version.
The end-to-end for how I envision this working is:
(1) Administrator creates a role (let's call it role A)
(2) Administrator assigns a user (or group) role A.
(3) Through the implementation of this feature, the administrator will be able to define which tracker-types that role A is capable of creating (so long as role A has been assigned the "add issue" permission)
(4) When the user possessing role A (and also having the "add issue" permission) clicks the "New Issue" tab, the user will see only those trackers which were defined as "can create this tracker" to role A.
(5) If the user has multiple roles with "can create this tracker" defined, each having their own set of permissible trackers, the user will be able to create the super-set of all trackers from all assigned roles.
This would truly be a GREAT and VALUABLE feature for Redmine's overall flexibility in configuration, and would be hugely appreciate by many!!
#24 Updated by budo kaiman almost 4 years ago
It would be great to have two options for this
- Permission to create issue of tracker
- Permission to view issues of tracker
The first one is really the most necessary, the second would be nice as it would prevent a complicated system of private issues as a workaround.
#29 Updated by Anton Titkov almost 4 years ago
Anton Titkov wrote:
Please check a plugin http://www.redmine.org/plugins/tracker_hider and share your thoughts. Thanks!
Has enybody tested the plugin?
It allows to hide issues under selected tracker for roles/users within a project. It solves the subject partly as i see.
It would be nice to get some feeback from you!
#31 Updated by Anton Titkov almost 4 years ago
alexandr al wrote:
http://www.redmine.org/plugins/tracker_hider does not solve the problem
I agree that the plugin doesn't solve the subject problem exactly by prescribed way, but you can hide trackers and get desired behavior despite in another way.
I have the feedback that it is really desirable to restrict an issue creation in a certain tracker depending on role https://github.com/atlascoder/tracker_hider/issues/1 . At this topic i also see that this feature is valued.
I agree and it will be implemented.
But i wonder if it is really needed to manage such restictions on the adminitration level? I think it is better to manage at the projec level, isn't it?