JIRA Throws Missing Available Workflow Actions
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
Problem
Some issues do not have any available workflow actions. Any conditions preventing workflow actions from not appearing are fulfilled.
The below error might appear in the atlassian-jira.log:
1
2
3
4
5
Caused by: java.lang.IllegalArgumentException: No workflow action with id '701' available for issue TEST-123
at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.getActionDescriptor(WorkflowTransitionUtilImpl.java:144)
at com.atlassian.jira.rest.v2.issue.UserResource.getActionDescriptorById(UserResource.java:304)
at com.atlassian.jira.rest.v2.issue.UserResource.findAssignableUsers(UserResource.java:289)
... 193 moreDiagnosis
Run the following query in your database:
Find out which workflow is associated to the affected issues:
1jira=> select w.name from jiraissue i, os_wfentry w where issuenum = <affected issue id> and project = (select id from project where pkey = '<affected project key>') and i.workflow_id = w.id;Find out the correct workflow with any issue that shows transition button:
1jira=> select w.name from jiraissue i, os_wfentry w where issuenum = <issue id> and project = (select id from project where pkey = '<affected project key>') and i.workflow_id = w.id;
Cause
This error is likely to be caused by a mismatch between the workflow step and the workflow itself.
One of the possible causes is hardcoding workflow step or action ID using custom code (for example groovy script in post function that points to an ID that doesn't exist)
Solution
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 (that has a different workflow), 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.
Copy the current Workflow Scheme, and re-assign the copied scheme to the affected project
Resolution
Resolution 1
For all of the following procedures, you must be logged in as a user with the Jira System Administratorsglobal permission.
Run the integrity checker via Administration >> System >> Integrity Checker. Fix the error if there is any error message being thrown.
Using the Integrity Checker
From the top navigation bar select Administration ⚙ > System.
Select Troubleshooting and Support > Integrity Checker to open the Integrity Checker page.
Or alternatively use: Keyboard shortcut: 'g' + 'g' + type 'integ'
Resolution 2
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Run the sql query to update the workflow name:
1
update os_wfentry set name = '<correct workflow name>' where id in (select i.workflow_id from jiraissue i, os_wfentry w where i.workflow_id = w.id and w.name = 'jira' and i.project = <project id>);Was this helpful?