Jira Data Center throws 500 error when accessing specific issues
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
Summary
Problem
When accessing specific JIRA issues, the Web UI throws a 500 error.
Solution
Error logs
The following appears in the atlassian-jira.log.
2018-07-12 12:09:37,846 https-jsse-nio-8443-exec-10 ERROR bobbie.price 729x203800x4 10ddopb 1.1.1.1,2.2.2.2 /browse/IS-45490 [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet action threw exception
java.lang.NullPointerException
at com.atlassian.jira.config.DefaultSubTaskManager.getParentIssueId(DefaultSubTaskManager.java:290)
at com.atlassian.jira.config.DefaultSubTaskManager.getParentIssueId(DefaultSubTaskManager.java:279)
at com.atlassian.jira.issue.IssueImpl.getParentId(IssueImpl.java:935)
at com.atlassian.jira.issue.IssueImpl.isSubTask(IssueImpl.java:928)
at com.atlassian.jira.issue.IssueImpl$1.create(IssueImpl.java:159)
at com.atlassian.jira.issue.IssueImpl$1.create(IssueImpl.java:156)Diagnosis
...
...Diagnostic Steps
When loading the backlog or accessing the issue directly, there are sub-tasks that have parents; determining the parent Issue ID from the sub-task fails.
It is caused by an inconsistency between the databases' issuelink and issuelinktype tables. These tables are responsible for holding the various Issue Link relationships that are available in your Jira instance. To diagnose the problem, execute the following query against the Jira database.
select * from issuelink where linktype not in (select id from issuelinktype);Resolution
Execute the following steps to resolve the issue.
Warning
The steps below involves direct manipulation of the database. We strongly recommend taking full database backups prior to proceeding.
Stop Jira
Run the following command to delete the bad links in the database
delete from issuelink where linktype not in (select id from issuelinktype);Start Jira
Was this helpful?