Project

General

Profile

Actions

Feature #17500

open

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

Feature #17500: Visibility/Use-ability/Creation Settings for Issue Trackers per Role per Project.

Added by James H over 12 years ago. Updated almost 10 years ago.

Status:
New
Priority:
High
Assignee:
-
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 3 (3 open — 0 closed)

Related to Redmine - Feature #17499: Issues Do Not Copy when Issue Tracker is Disabled from "Copy From" ProjectNewActions
Related to Redmine - Feature #19003: Selection of User/Role -based Settings e.g. Email Notification & Issues VisibilityNewActions
Related to Redmine - Feature #850: Per-project role permissionsNewActions
Actions

Also available in: PDF Atom