The default permission scheme changed

[Any Russenberger]

Hi Comunnity! I'm having a problem I can't resolve, because I don't know how it happened.

All the projects manage by the organisation that we create, are linked to a Permission Scheme different to the default one... 

Can someone tell me how Jira determinates the default scheme to apply for a new enterprise managed project?

I prefere it use the historical Default Scheme, that the one it's using now. And I read you can't select a specific scheme for new projects. 

Can someone help me to understand this? Thank you very much!!

[Trudy Claspill · Accepted solution]

Hello @Any Russenberger 

The default schemes are determined based on the project Template that you select.

During creation of the project you can opt to Share the configuration of an existing product. That would cause the new project to use the same Permission, Issue, Field, Notification, Screens, and Workflows schemes as the specified project. That is the only way to specify a different scheme specifically during project creation.

However, after a project has been created, a Jira Administrator can change which schemes are used by that project. The Jira Administrator can change the Scheme used for each area separately, so they could choose to set all Projects to use the same Permission scheme while also allowing them to use individually customized schemes for other elements.

[Any Russenberger]

Hi Trudy! How are you? Thanks a lot for taking the time, and for your answer...

I'm afraid, that's exactly the problem...  If I don't share the configuration with any project, or stablished an specific project category, Jira will still use a specific Permission Scheme (created by me, for a rare project I made a long time ago), and not the Default one... I want it to use the Default Scheme for new projects.

After that, now I'm just changing the scheme permissions manually inside every new project that someone creates...

I really don't know how it happened... and how to solve it... 

[Trudy Claspill]

Hello Anabella,

What type of project is picking up your custom scheme; a Software, Service, or Work Management project?

What are the exact steps being used to create the new project in this case where the project is ending up with your custom scheme?

[Any Russenberger]

Good morning Trudy!

My team es creating Kanban or Scrum projects, managed by the organisation. 

I noticed this problem when a new user creates a new project, and inmediately, the same user (being Responsable and creator of that project) couldn't get in because a permissions problem. "You don't have permission", and he was the recently creator.... 

Then I get in as Admin, check the project configuration, and saw the permission scheme there... I tried to create new project and the same thing happened, and with other users too. 

I have to configurate of every single new project, and change the scheme manually... Jira won't let them in, because the new team doesn't belong to that scheme roles... When I change the scheme, the creator and users asigned can get in a use the project normally...

About the steps... We are not selecting any project related for configuration (I tried it myself).

Image 1: Last step before creating a project...

Image 2: Go to config resume, and there it is: a permission scheme that only apllies for 1 project, and not all of them. :(

[Trudy Claspill]

Hello @Any Russenberger 

Based on the image you pasted, you are creating Software projects that are Company Managed.

In a Jira Cloud only a Jira Administrator can create a Company Managed project. End users that are not granted the Jira Administrator role cannot create Company Managed projects unless you have a third party app that somehow enabled that. So, that is one puzzling element to this.

When a new project is being created and one selects the Create Project option either from the Projects menu or from the View All projects screen. The first thing that is shown is usually a screen similar to this:

The options on the left depend on which Jira products you have installed; Jira Software, Jira Service Management, and/or Jira Work Management. This is the step where a project template is chosen.

Reviewing my own Jira Cloud Free instance again, I found that I misspoke. I thought that new projects would get assigned the default permission scheme, but I see that they are getting a uniquely named permissions scheme. I assume it is being made as a copy of the Default Permission Scheme, but I'm not positive.

I recommend that you open a support case directly with Atlassian to investigate this further. They would be able to connect to your system, with your permission, to dig into the details of its configuration. Cases can be opened by Jira Administrators, Site Administrators, and Organization Administrators.

https://support.atlassian.com/contact/#/

[Any Russenberger]

Thanks a lot Trudy!

I really appreciate the time and your answer! Yes, I gave some users Admin permissions, because Company managed projects are more complete. And honestly, we're still studying Jira!

I will follow your recommendation and contact support for this!

I'll share de answer here too!! :D

[Any Russenberger]

@Trudy Claspill  good morning!!

I'll share you the answer of Atlassian Support. Thanks for your help!

"So far, Jira is assigning the first permission scheme that is listed alphabetically, instead the default one.

There is a feature request opened to change that and makes Jira to consider the default scheme instead of the first one listed alphabetically: Jira Cloud 16703

It looks like Jira ignores all "default"schemes. This is going to change with the feature request.

By now, you can try to create a scheme do be used as default, naming it with some name that starts with the letter A. Other thing you can is: in the project creation, there is a button called Share Settings with Existing Project. You can select one previous project that contain the same schemes you want to use in the new one."

[Trudy Claspill]

Thank you for sharing what you learned!

For those who like links, here is the issue link:

https://jira.atlassian.com/browse/JRACLOUD-16703

[Mykenna Cepek]

From Atlassian in '16703:

After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-59453 – Ability to Change Default Permission Scheme which has more votes.