Symptoms

In some JIRA projects users are unable create issues, even if the necessary user has the required permissions to do so. Sometimes, this will occur directly after an upgrade. In the logs the following exception will appear:

Cause:
com.atlassian.jira.exception.IssueNotFoundException: Issue with id 'null' or key 'null' could not be found in the system

Stack Trace: [hide\]

com.atlassian.jira.exception.IssueNotFoundException: Issue with id 'null' or key 'null' could not be found in the system
at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.getIssue(AbstractIssueSelectAction.java:129)
at com.atlassian.jira.web.action.issue.CreateIssueDetails.getIssue(CreateIssueDetails.java:116)
at com.atlassian.jira.web.action.issue.CreateIssueDetails.doPostCreationTasks(CreateIssueDetails.java:108)
at com.atlassian.jira.web.action.issue.ExtendedCreateIssueDetails.doExecute(ExtendedCreateIssueDetails.java:35)
at com.opensymphony.workflow.WorkflowException: Could not load validator class

Diagnosis

1. Browse to the appropriate project administration screen.
2. From there, browse to the workflow in use.
3. Find the transition that's throwing the error.
4. Note the particular validator. The validator will specify a code that suggests which plugin you need. Check the resolution for the known plugins that cause this issue.

Cause

Some JIRA instances rely on 3rd party workflow validator tools to set conditions, validators or post-functions on an issue during it's lifecycle at some issue operation or transition within a workflow. JIRA will lazily load any 3rd party classes required at the first time of use. If the class is not present, the issue creation may fail.

Resolution

1. Download the applicable Jar from the vendor. A clue of the plugin responsible is often yielded from the stack trace; check for the name of the vendor. The set of known plugins to cause this issue include:
   1. JIRA Suite Utilities
   2. JIRA Misc Utilities
   3. Minyaa Suite
   4. JIRA Email This Issue
      Be sure to use the correct version, and also to remove any previous version of that plugin.
2. Once installed, restart JIRA.