Jira Automation fails to transition an issue to destination status

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

Automation is attempting to transition a Jira issue to a specific status. It fails with error:

"Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)"

Most common causes

There are two main causes for the automation error:

  1. The automation rule has a destination status, but there is no transition from the current status to the new status  in the workflow of the affected issue
  2. The user does not have the permissions to transition the issue

Confirm the workflow has an applicable transition for Automation to use

If your destination status does not have a transition from the issue's current status, then Jira Automation will not be able to set the status as configured.

You'll need to edit your project's workflow to allow for one of the following:

  • Create a direct transition from the current status to the new status in the workflow of the issue
    OR
  • Configure the destination status in your workflow editor using the checkmark "Allow all statuses to transition to this one"

Diagnose and resolve permission-related problems

If the transitions in your workflow editor are correct, confirm the affected user has the permissions to transition issues in this project.

We'll first need to know which user is executing the automation, and what Actor the rule is configured to use.

Check which Actor is configured by the automation rule

As a Jira Administrator:

  1. Visit gear Settings > System
  2. Select Global Automation
  3. Search or scroll to find the automation rule and select it
  4. Under Rule details, check the value of the Actor selector

If the Actor is set to "User who triggered the event," or to a specific user, this user must have the Transition issues permission in your selected project. 

If the Actor is set to "Automation for Jira," then the "atlassian-addons-project-access" role must have this permission.

Check the Transition issues permission in your project

As a Jira Administrator:

  1. Visit your affected project, and select Project Settings
  2. Select Permissions
  3. Scroll to the Transition issues permission

Ensure that this permission is granted to the "atlassian-addons-project-access" project role, along with any other groups, roles, or users who are affected by the automation error.

Check the workflow for conditions and status properties

If the issue is still present, your project's workflow may have conditions or properties configured that limit the ability to transition issues.

To confirm, visit your project's workflow editor and investigate for any workflow transition conditions or status properties. If you find items that restrict these, you can make any changes you find necessary to allow the proper users to transition.


Last modified on Feb 6, 2025

Was this helpful?

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