Error rendering 'com.atlassian.jira.jira-view-issue-plugin:timetrackingmodule'
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 particular issues shows the following error:
Error rendering 'com.atlassian.jira.jira-view-issue-plugin:timetrackingmodule'. Please contact your JIRA administrators.
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
2015-01-26 15:09:11,209 http-bio-8014-exec-21 ERROR matheus 909x54x1 1fg0cr8 192.168.10.239 /browse/DEMO-1 [jira.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-view-issue-plugin:timetrackingmodule (null)
java.lang.NullPointerException
at com.atlassian.jira.security.DefaultPermissionManager.doIssuePermissionCheck(DefaultPermissionManager.java:284)
at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:207)
at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:111)
at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:202)
at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:104)
at sun.reflect.GeneratedMethodAccessor263.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)Diagnosis
Run the following queries in JIRA's database - if anything is returning, please continue to the "Workaround" section:
1
2
3
SELECT il.* FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.destination WHERE ji.issuenum IS NULL;
SELECT il.* FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.source WHERE ji.issuenum IS NULL;You can see with the queries below which issues are being affected by this problem:
1 2 3SELECT p.pkey, ji.issuenum FROM jiraissue ji JOIN (SELECT il.* FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.destination WHERE ji.issuenum IS NULL) AS pl ON pl.source = ji.id JOIN project p ON ji.project = p.id;1 2 3SELECT p.pkey, ji.issuenum FROM jiraissue ji JOIN (SELECT il.* FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.source WHERE ji.issuenum IS NULL) AS pl ON pl.destination = ji.id JOIN project p ON ji.project = p.id;ℹ️ The issues returned with this second query will not display the same errors described above, but still are part of orphaned links that should be removed.
Workaround
⚠️ Backup JIRA!
Stop JIRA.
Run the following SQL statements in JIRA's database:
1 2DELETE FROM issuelink WHERE id IN (SELECT il.id FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.destination WHERE ji.issuenum IS NULL); DELETE FROM issuelink WHERE id IN (SELECT il.id FROM issuelink il LEFT JOIN jiraissue ji ON ji.id = il.source WHERE ji.issuenum IS NULL);Restart JIRA.
After that you should no longer see problems viewing those issues.
Was this helpful?