Browsing Selected Issues Results in an IllegalArgumentException

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

Viewing an issue results in a stack trace like:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 java.lang.IllegalArgumentException: The entity passed must not be null at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:186) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:64) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:119) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:199) at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:64) at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:119) at sun.reflect.GeneratedMethodAccessor987.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:70) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at $Proxy227.hasPermission(Unknown Source) at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.getIssue(AbstractIssueSelectAction.java:93) ...

Cause

One or more issues are associated with a project that doesn't exist.

Resolution

  1. Using the database integrity checker, run the "Check Issue for Relation 'ParentProject'" check and fix any errors that are reported.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.