Jira Errors due to non-existing status

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Problem

When attempting to perform various actions it fails with errors.  This includes searches, viewing issues, view Agile boards, creating Agile boards, etc.

The following errors may appear in the atlassian-jira.log, depending on the various actions:

2018-08-08 09:23:41,367 https-jsse-nio-8443-exec-20 WARN admin 563x439985x1 4het9v 0:0:0:0:0:0:0:1 /secure/QueryComponent!Jql.jspa [c.a.jira.workflow.AbstractJiraWorkflow] Workflow 'Test Workflow' contains step 'In Progress' (ID:17) which is linked to non-existing status (ID:12345)

2018-08-08 10:07:23,972 https-jsse-nio-8443-exec-17 WARN admin 607x445953x1 j8un30 0:0:0:0:0:0:0:1 /secure/QuickSearch.jspa [c.a.jira.workflow.AbstractJiraWorkflow] Workflow 'Test Workflow' contains step 'In Progress' (ID:17) which is linked to non-existing status (ID:12345)

2018-08-08 09:06:13,666 https-jsse-nio-8443-exec-29 WARN admin 546x438605x1 1gsdonq 0:0:0:0:0:0:0:1 /rest/greenhopper/1.0/rapidview/create/advanced [c.a.jira.workflow.AbstractJiraWorkflow] Workflow 'Test Workflow' contains step 'In Progress' (ID:17) which is linked to non-existing status (ID:12345)

2018-08-08 09:03:25,953 https-jsse-nio-8443-exec-15 WARN admin 543x438362x1 y635u9 0:0:0:0:0:0:0:1 /browse/TEST-5619 [c.a.jira.workflow.AbstractJiraWorkflow] Workflow 'Test Workflow' contains step 'In Progress' (ID:17) which is linked to non-existing status (ID:12345)

2018-08-08 08:57:53,339 https-jsse-nio-8443-exec-16 WARN admin 537x437593x1 y635u9 0:0:0:0:0:0:0:1 /issues/ [c.a.jira.workflow.AbstractJiraWorkflow] Workflow 'Test Workflow' contains step 'In Progress' (ID:17) which is linked to non-existing status (ID:12345)

Diagnosis

From the errors above, we know the following information:

  • The workflow involved is "Test Workflow"
  • The Step that is linked to a missing project is Step with ID 17
  • The Status ID that is expected, but missing, has the ID 12345

If we check the database, we can confirm that there is no Status with ID 12345:

SELECT * FROM issuestatus WHERE id = '12345';

Resolution

Remove the step that is linked to a non-existing status. 
If removing the step fails, follow the document below:

Determine the ID of the missing Status
  • Export the Workflow to XML  (While editing the workflow, click  Export > As XML)
  • Open the XML and search for the step/status name.  For example, in the above screenshot, we see DELETEMESTATUS
    • You will see something like this:

          <step id="12" name="deletemestatus">
            <meta name="jira.status.id">10200</meta>
          </step>
  • In this example case, the ID is 10200
Workaround - Database Fix

Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

  1. Create a brand new status ( Jira Admin > Issues > Statuses > Add status)
    1. For this example, I will name the new status "deletemestatus2"
  2. Access the database and run the following query:

    SELECT * FROM issuestatus WHERE pname = 'deletemestatus2';
    1. Take note of the ID that is returned from the SQL query
  3. We now have the ID from the problematic workflow step, 10200, and the ID from the newly created status.
  4. Update the newly created status to use ID 10200.
  5. UPDATE issuestatus SET id = '10200' WHERE id = 'XXXXX';
    1. Replace XXXXX with the ID from in from step 2 above.
  6. Next, we need Jira to refresh caches to reflect the new database change. To do this, create yet another new status, just like from step 1.
  7. Finally, go back to editing the workflow and remove the workflow step.
  8. You can also clean up the additional statuses that we created.


Last modified on Nov 30, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.