Changing the default permission scheme

In JIRA, the application ships with a "Default Permissions Scheme" already prepared, and it is described as the scheme that is automatically assigned to any new project.

If you remove all projects from this scheme, you are able to delete the scheme. Creating a new scheme afterwards, doesn't give any indication whether its the default. So, now, if you have multiple schemes, and you've deleted the 'default,' it is no longer apparent which scheme is now the default, nor is it apparent how to set the default.

How does one set the default permissions scheme that is used for new projects?

7 answers

The default scheme that was being applied is called *Default software scheme* for me. Trying to be clever I deleted this scheme, then renamed *Default Permission Scheme* to *Default Software Scheme* thinking, that'll now mean the default gets set. But no, Jira was wise to this attempt to make it behave sensibly and has a built in defeat for this tactic  - on the next project that was created, it went and created a new Permission scheme called *Default software scheme - 1

I find this behaviour annoying but I guess this issue has only been open for 6 years so I'm probably just being impatient.

In my case a scheme other than the Default Permission Scheme was the actual default (no idea how it was set). 

you should me missed something - default shema can't be deleted

It would seem sensible to be able to copy the default scheme, edit it and then set the new scheme as the default- is this really not possible?

I have the same problem as @Adam Hubscher

I have the same problem.  It appears that a scheme other than the Default Permission was set-up and I have no idea how that was set up but I can tell that it was done recently because all of a sudden my new projects have that scheme.   It was not set up correctly which caused issues.  I have another scheme that I prefer to be the default but don't know how to make that happen.

 

0 votes
Joseph Pitt Community Champion Jul 24, 2017

This doesn't fix your problem, but I suggest you treat JIRA as a production system and put it under change control. Then give anyone who doesn't follow the process a couple days off without pay. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

47 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you