-
Suggestion
-
Resolution: Unresolved
-
None
-
17
-
38
-
Problem definition
- Currently, if you are a Jira Administrator your role as complete access to the Default configurations for every project either company or team managed
Impact
- Some administrators can change inadvertently some configurations and break some projects workflows, etc…
Suggested resolution
- Add the possibility to allow a more granular role-based permission model to allow the lockdown of some features/configurations for particular users with Admin Role in Jira. ( edit workflow, screens within the project, issue type creation, etc.)
- is related to
-
JRACLOUD-84405 [Tracked in Issue Links] Jira permissions related feature requests
- Gathering Interest
- relates to
-
JRACLOUD-62881 Extended Project Admin Permissions - Workflow Management
- Closed
(1 mentioned in)