JIRA Documentation

JIRA 6.3
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

Some issues do not have any available workflow actions. The issues which are missing the available workflow actions do not have any condition. Even if they do, the condition is being met.

Cause

This error is likely to be caused by a mismatch between the workflow step and the workflow itself.

Workaround

  • If you are not a JIRA administrator or cannot run the integrity checker (see solution below), you can move the issue to another project, and then move it back to original project. The workflow actions should be available again.
  • Clone the problematic ticket and the cloned ticket will shown the workflow actions again.

Resolution

Run the integrity checker via Administration >> System >> Integrity Checker. Fix the error if there is any error message being thrown.

Related Content

 Expand to see related content
Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4 Comments

  1. I also saw this problem when my workflow had some conditions/validators from plugins I didn't have installed in that particular instance of JIRA (in case someone else sees this problem and the integrity checker doesn't fix it, another thing to check).

  2. Another possibility: check that all custom fields in workflow screens are actually associated with the issue type(s).

  3. We have found that it is sufficient to change the issue type when doing the move. This causes the actions to reappear, and then they are retained when the issue type is restored. This less drastic workaround has the added benefit of leaving the issue key unchanged. 

  4. We had this issue and it was caused by incorrect project permissions. For unknown reasons the default permission scheme didn't allow users to resolve issues.