How to restrict scheme change permission by project?

[Brad]

We are currently creating separate schemes for each project, so teams can configure it based on their requirements.

We would like to be able to give project admins the flexibility to modify their own project schemes. However, we cannot find a way to limit scheme changes by project.

Is there a way to give each project admin access to their own project’s configuration scheme without granting them access to other project schemes?

[Nic Brough -Adaptavist- · Accepted solution]

No. You're either an admin, or you're not. There's no way to delegate this.

It is being looked at though - see https://jira.atlassian.com/browse/JRA-3156

For now, you'll need to be creative as Fabio says - make extensive use of roles in schemes, because your project admins can control who goes into which role (ideally, don't use groups at all in permission schemes)

[Daniel Wester]

We just listed Delegated Administrator for JIRA https://marketplace.atlassian.com/plugins/com.wittified.jira.delegated-admin which allows you to delegate the administration of project schemes to the project lead while still maintaining control as an administrator.

[Nic Brough -Adaptavist-]

<sound of bookmarks being added>

[Fabio Racobaldo _Catworkx_]

Hi Brad,

in my opinion the best way to do that is to manage the project permission scheme using the project roles. Each project administration can manage users/groups in specific project role.

Hope this helps.

Fabio