Prohibit the use of Permission Scheme for multiple projects

[Nickolai Korzan]

Hi,

Is it possible to prohibit the use of Permission Scheme for multiple projects? Purpose: one project - one scheme.
Ultimately, it is necessary that the scheme could be changed either by one user or it could be assigned for only one project

[Lenin Raj]

Hi @Nickolai Korzan 

I know you have asked this question for Jira server, but there is solution for Jira Cloud.

You could take a look at Next Gen Projects. Each Next Gen project has their own independent permission schemes. So you won't have the problem of one scheme affecting another project inadvertently.

This article compares classic and next gen projects: https://confluence.atlassian.com/jirasoftwarecloud/working-with-next-gen-software-projects-945104895.html

- Lenin

[Jack Nolddor [Sweet Bananas]]

Hi Nickolai and Welcome,

Sadly, there is no way to restrict shared Permission Scheme on Jira. Moreover, is a good practice to groups similar projects into the same schemes to avoid administration overhead.

Also more schemes means a performance degradation over time.

Kind Regards

[Nickolai Korzan]

Thanks for your reply. Are there any plugins that can solve this problem?
Is it possible to customize JIRA yourself? (change source code, write plugin)

[Lenin Raj]

Hi @Nickolai Korzan 

If you are the project admin, one recommendation is to keep the admin permissions with one person and the permission schemes are modified through the same person.

[Nickolai Korzan]

Our problem is that we have several administrators. And we need to do so that only the administrator who created it can change the scheme

[Lenin Raj]

In this case, only team coordination between the project admins will be helpful. If everyone has the same level of permissions, it is hard to put system level constraints.