Empty Status Appear In Issue Navigator
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
Summary
Symptoms
When any project and an empty status selected, JIRA displays a stack trace.
A generic "Oops - an error has occurred" message may appear in the front-end UI.
The following appears in the
atlassian-jira.log:
1
2
3
4
5
6
7
[500ErrorPage.jsp] Exception caught in 500 page null
java.lang.NullPointerException
at com.atlassian.jira.issue.search.searchers.transformer.StatusSearchContextVisibilityChecker.FilterOutNonVisibleInContext(StatusSearchContextVisibilityChecker.java:31)
at com.atlassian.jira.issue.search.searchers.transformer.NavigatorStructureChecker.checkValue(NavigatorStructureChecker.java:162)
at com.atlassian.jira.issue.search.searchers.transformer.NavigatorStructureChecker.checkOperand(NavigatorStructureChecker.java:119)
at com.atlassian.jira.issue.search.searchers.transformer.NavigatorStructureChecker.checkSearchRequest(NavigatorStructureChecker.java:79)
at com.atlassian.jira.issue.search.searchers.transformer.IdIndexedSearchInputTransformer.doRelevantClausesFitFilterForm(IdIndexedSearchInputTransformer.java:97)
Diagnosis
Confirmed the status exist in the database and the JIRA UI. In the database, run the following SQL query:
1
select id,pname from issuestatus;ℹ️ ensure that the total number of status exist in the database match the status listed in the UI via Administrations > Statuses
Cause
There is non-existing status linked to any step in active workflow. The problematic Workflow will have empty Linked Status:
ℹ️ download the Workflow's XML to confirmed what is the non-existence status's ID that is being used in the workflow
Solution
Resolution
There are two option to fix this behaviour:
recreate the status that is referred in the workflow's step
copy the problematic workflow and correct the Linked Status. Then, Activating workflow copy.
Was this helpful?