Unable to create new project, can't assign default permission scheme

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

When creating a new project, a java.lang.NullPointerException will be thrown

  • Seems like JIRA cant assign the new project to the Default Permission Scheme

The following appears in the atlassian-jira.log

1 2 3 4 5 6 7 8 java.lang.NullPointerException at com.atlassian.jira.projectconfig.contextproviders.ProjectPermissionContextProvider.getContextMap(ProjectPermissionContextProvider.java:85) at com.atlassian.jira.plugin.webfragment.CacheableContextProviderDecorator.initContextMap(CacheableContextProviderDecorator.java:70) at com.atlassian.jira.plugin.webfragment.CacheableContextProviderDecorator.getContextMap(CacheableContextProviderDecorator.java:46) at com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel.getHtml(DefaultWebPanelModuleDescriptor.java:144) at com.atlassian.jira.projectconfig.tab.WebPanelTab.getTab(WebPanelTab.java:75) at com.atlassian.jira.projectconfig.servlet.PanelServlet.outputTab(PanelServlet.java:163) at com.atlassian.jira.projectconfig.servlet.PanelServlet.doGet(PanelServlet.java:136)

Diagnosis

Environment

  • A modification of the permission scheme table was done

  • The original default permission scheme is missing/deleted. Is this is missing, JIRA will encounter the nullpointerException error as it cant find the default permission scheme.

Diagnostic Steps

1 2 3 select * from permissionscheme; select * from project where id not in (SELECT source_node_id FROM nodeassociation where sink_node_entity = 'PermissionScheme');
  • 1st query - Verify if the default permission scheme with id = 0 exist

  • 2nd query - To filter out which project has lost the permission scheme

Cause

Missing default permission scheme.

Solution

Resolution

Backup up your JIRA prior to below action

  1. Go to JIRA Administration , Issues > Permission Scheme

  2. Create a new permission scheme called JIRA Default Permission Scheme, with default permission setup

  3. Do not assign any project to this permission

  4. Stop JIRA

  5. Go to database

  6. select * from permissionscheme; to find the newly created JIRA Default Permission Scheme

  7. Note the ID, will be shown as xxx in below query. Replace accordingly.

  8. update permissionscheme set ID=0 where ID=xxxx

  9. Start JIRA

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.