Feature #17500

Visibility/Use-ability/Creation Settings for Issue Trackers per Role per Project.

Added by James H almost 8 years ago. Updated over 5 years ago.

Status:NewStart date:
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Issues permissions
Target version:-
Resolution:

Description

Requesting feature for allowing setting visibility and use-ability settings for Issue Trackers per role per project.

Would like to have a way to:
  • Allow only certain roles to create certain issue tracker issues for a particular project.
  • Allow certain roles the ability to "edit" or "update" that particular issue tracker type.
  • Allow certain roles the ability to view that particular issue tracker type.
  • Disallow certain roles from being able to view that particular issue tracker type.

Related issues

Related to Redmine - Feature #17499: Issues Do Not Copy when Issue Tracker is Disabled from "C... New
Related to Redmine - Feature #19003: Selection of User/Role -based Settings e.g. Email Notific... New
Related to Redmine - Feature #850: Per-project role permissions New 2008-03-14

History

#1 Updated by Alain V. almost 8 years ago

I fully support this.

In our organisation we do have a project with feature and defect and we would like the role tester can ONLY create defect type ticket and not feature.

#2 Updated by Lajish Lakshmanan almost 8 years ago

+1

#3 Updated by Toshi MARUYAMA almost 8 years ago

  • Related to Feature #17499: Issues Do Not Copy when Issue Tracker is Disabled from "Copy From" Project added

#4 Updated by Benedikt Aufermann over 7 years ago

I support this also.
We want to have a full transparency until a certain level. But the concrete "Tasks" for a person should not been seen by a bigger audience.

#5 Updated by Lajish Lakshmanan over 7 years ago

Hi All,

I think tracker wise control can be handled through this plugin http://www.redmine.org/plugins/redmine_track_control
As this is a plugin and not a core part of redmine, but for the time being, this plugin will quench your thirst.

Hi Toshi MARUYAMA,

It is my humble request to include this in redmine core asap.

#6 Updated by James H over 7 years ago

@Lajish
Have you tried the plugin? If so, what version of redmine?

I for one, cannot get those plugins to work on any of the newer versions.

#7 Updated by Lajish Lakshmanan over 7 years ago

James H wrote:

@Lajish
Have you tried the plugin? If so, what version of redmine?

I for one, cannot get those plugins to work on any of the newer versions.

I didn't try it. But I will test it in my Test Server and let you know about its status very soon.

#8 Updated by Lajish Lakshmanan over 7 years ago

Hi there,

I tried this plugin in 2.4.2 & 2.5.2 version and it worked fine. This plugin helps you to set role wise control over tracker creation...:)

#9 Updated by James H over 7 years ago

Hmm.. I tried it on those versions..

I get errors when trying certain things; and when creating issues, it behaves oddly. I cannot get it function correctly.
The names of the trackers also is bugged, but thats just cosmetic.

You have tried testing out creating issues with different users/roles?
Installation of the plugin goes smoothly, but the actual functionality with redmine as a whole does not work for me.

#10 Updated by Toshi MARUYAMA about 7 years ago

  • Related to Feature #19003: Selection of User/Role -based Settings e.g. Email Notification & Issues Visibility added

#11 Updated by Alexis Parent over 6 years ago

+1

#12 Updated by Wim DePreter over 5 years ago

FTR: #285 does already great part of this feature (except "per project")

#13 Updated by Toshi MARUYAMA over 5 years ago

  • Related to Feature #850: Per-project role permissions added

Also available in: Atom PDF