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?
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.
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.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events