NullPointerException on the Dashboard after an Upgrade

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

Symptoms

After upgrading Jira, navigating to the dashboard results in NullPointerException:

1 2 3 4 5 6 7 We were unable to render this portlet due to an internal error. Please contact your Jira Administrator. Exception thrown while rendering portlet of type 'Projects' with id of '10001' on dashboard with id '10000' java.lang.NullPointerException at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:342) at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasPermission(DefaultPermissionSchemeManager.java:314) at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemeAuthority(DefaultPermissionSchemeManager.java:238) at com.atlassian.jira.security.AbstractPermissionManager.hasProjectPermission(AbstractPermissionManager.java:253) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:195)

Cause

If this problem starts happening after uninstalling or disabling Jira Service Management, please refer to JSDSERVER-337 - JIRA Stops working after Disabling or Uninstalling JIRA Service Desk instead.

The Current Reporter Browse Project Permission was enabled in the previous Jira installation and the modifications have not been in the current Jira installation.

Resolution

Apply the permission customization to the new Jira instance. See Current Reporter Browse Project Permission.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.