Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

New JIRA Install - Integrity Checker: Duplicate Permission: SchemePermissions (ID: 10101)

I just setup a new JIRA server.  JIRA 7.5.2.

The install showed no errors. 

The integrity Checker Pass everything but

  Check for Duplicate Permissions Check the permissions are not duplicated

ERROR: Duplicate Permission: SchemePermissions (ID:10101)

What do I need to do?  Is this anything to worry about.

I have hardly done anything within JIRA so far.

3 answers

Same error on a Jira Data Center 9.1.1 brand new, and empty install

'Jira Data Center' evaluation ('Express Install' > use the internal H2 database)

Brand new install:

  • no users (other than the initial Jira Admin user created at first start up)
  • new projects, therefore no issues.
  • 'out-of-the-box' config

I've just been exploring all the Jira Admin stuff and then came to this one:

"ERROR: Duplicate Permission: SchemePermissions (ID:10101)" - same as everybody else

Googling for "ERROR: Duplicate Permission: SchemePermissions (ID:10101)" shows only this page; it's not mentioned anywhere else on an webpage (e.g. not in their[known defects])

Curious, I checked our 3yo production Jira:  same problem there.

It's a known problem (from all the comments + personal experience), but not logged as a bug.

This continues to happen, with every new installation of Jira Server...

0 votes
Dave Theodore [Coyote Creek Consulting]
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 15, 2017

I consider this a bug, but my opinion is not shared by all.  Essentially there are race conditions on certain functions in JIRA. They can happen when user activity is occurring at the same time you make changes to underlying Project infrastructure. My guess is that you were changing something to do with Permissions at the same time that a user was doing something on an issue that touched whatever permission function you were changing. Just "fix" the problems in the Integrity Checker, run it again to make sure there are no more issues and you should be good to go.

In the future, I recommend making changes to Workflow Schemes, Permissions and other changes to existing fields, Workflow, etc during low usage periods to avoid this race condition. Adding new fields, Issue Types, Workflows, etc are safe to do any time. You want to avoid changing something that someone could be in the middle of working on at the time you say go, though. This is typically what triggers the problem.

This is a brand new install.  I haven't released it to the company yet.  So there were no users in it but me.

Thanks for the info.  

Just installed 8.4.0. No users accessing the system. Same error. 2020/01/06

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events