Hi all,
After doing a bit of tidying up (i.e. removing redundant projects) we can no longer access Kanban boards in Jira (Scrum boards are fine) as the Jira instance throws the below error:
2018-03-23 10:15:39,602 http-bio-8080-exec-9 ERROR marcus.monaghan 615x182284x2 m46fbh 192.168.133.32,127.0.0.1 /rest/greenhopper/1.0/xboard/work/allData.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: The Project argument and its backing generic value must not be null
java.lang.IllegalArgumentException: The Project argument and its backing generic value must not be null
at com.atlassian.jira.security.DefaultPermissionManager.doProjectPermissionCheck(DefaultPermissionManager.java:251)
at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:171)
at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:98)
at sun.reflect.GeneratedMethodAccessor406.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
Having searched for previous issues I found the below which seemed to be the most relevant but following these instructions hasn't resolved the issue (even though there was orphaned data).
I don't suppose anyone else has any other suggestions?
Thanks,
Marcus
Hi Mj,
You mentioned that other thread, but I think it's just referring this this KB JIRA Functionality Fails due to The Project argument and its backing generic value must not be null Error
Just want to confirm that you first followed those steps.
Next, at the very bottom of that KB there are additional steps to follow if this didn't solve the issue:
If the above does not solve the problem, please see JIRA: System Error When Project Administrator Trying to Access the Permission Page for further information as it may be related.
Between these two KBs and their steps, I believe you should be able to recover from this error. Please note that you probably should generate a backup before making these changes, and in turn I would also recommend stopping Jira before you make any changes directly to the database like this.
Please let us know the results.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.