nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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!!

Accepted answers

Trudy P Claspill

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.

All comments

Trudy P Claspill

Hello @Any Russenberger

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

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 P 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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud