JIRA: System Error When Project Administrator Trying to Access the Permission Page
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
This screen was shown when a normal jira-user has been given a Project Administrator role, and the user tries to access a Project Permission Page:
The following exception can be found within the atlassian-jira.log or by expanding the Technical details section of the error page above:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Cause
Referer URL: https://your.url.com/plugins/servlet/project-config/yourproject
java.lang.IllegalArgumentException: The Project argument and its backing generic value must not be null
at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:154)
at com.atlassian.jira.security.AbstractPermissionManager.hasPermission(AbstractPermissionManager.java:137)
at sun.reflect.GeneratedMethodAccessor181.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:83)
at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
at com.sun.proxy.$Proxy93.hasPermission(Unknown Source)
at com.atlassian.jira.bc.project.ProjectAction.hasPermission(ProjectAction.java:70)
at com.atlassian.jira.permission.DefaultProjectPermissionSchemeHelper.hasEditPermission(DefaultProjectPermissionSchemeHelper.java:50)
at com.atlassian.jira.permission.DefaultProjectPermissionSchemeHelper.getSharedProjects(DefaultProjectPermissionSchemeHelper.java:39)
at sun.reflect.GeneratedMethodAccessor1951.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)
at com.sun.proxy.$Proxy498.getSharedProjects(Unknown Source)
at sun.reflect.GeneratedMethodAccessor1951.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)
at com.sun.proxy.$Proxy498.getSharedProjects(Unknown Source)
at com.atlassian.jira.projectconfig.contextproviders.ProjectPermissionContextProvider.getContextMap(ProjectPermissionContextProvider.java:86)
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:177)
at com.atlassian.jira.projectconfig.servlet.PanelServlet.doGet(PanelServlet.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
...Cause
Some issues are still referring to projects that were deleted.
Resolution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Stop JIRA.
Create a backup of your database.
Run the following query:
1 2 3 4DELETE FROM nodeassociation WHERE source_node_entity = 'Project' AND source_node_id NOT IN (SELECT id FROM project); DELETE FROM jiraissue WHERE project NOT IN (SELECT id FROM project); DELETE FROM projectversion WHERE project NOT IN (SELECT id FROM project); DELETE FROM component WHERE project NOT IN (SELECT id FROM project);Start JIRA.
Perform a Full re-index on your JIRA instance to successfully retrieve the updated value from database.
ℹ️ If the above query does not solve the problem, please see also: Jira Data Center functionality fails due to the error The Project argument and its backing generic value must not be null for further information.
Was this helpful?