JIRA 7 has landed! Are you an existing JIRA user with questions about upgrading? Visit the Migration Hub for information about upgrading to new JIRA applications

Skip to end of metadata
Go to start of metadata


Any of the below actions results in the example Stack Trace below.

  1. Accessing Issues
  2. Browsing the Project Summary
  3. Filtering Issues by a Field

The following appears in the atlassian-jira.log:


This particular case has two known causes:

  1. One or more Versions are pointing to one or more Projects that no longer exist.
  2. One or more Statuses are used by a Workflow and no longer exist.


Verify if there are missing Versions with Projects attached to them with the below SQL:

If rows are returned from the above SQL, follow these instructions to remove them:

  1. Back up JIRA.
  2. Shut down JIRA.
  3. Run the below SQL.
  4. Restart JIRA and test to ensure the exception is not presented.

Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.

(info) The provided SQL examples above are PostgreSQL and the syntax may need to be modified depending on your JIRA database.

If the above does not fix the problem, check if any Statuses are missing:

  1. Enter the Workflow Designer for the JIRA issue(s) that are experiencing problems.
  2. Confirm that that the statuses listed in the workflow are loaded in JIRA.
  3. If any are missing, add them in manually.
  4. Test and see if the problem is fixed.
Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?