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.)