Azure DevOps transitions throw synchronization errors

 Problem

An error message like ‘No transition to the desired status’ appears when transitioning items from ADO to Jira.

Open

 Solution

This error usually happens when the Jira workflow does not have global transitions, which is how Azure DevOps workflows work.

Open

Transitions in Jira

Global transitions are strongly recommended when working on initial synchronizations and continuous synchronizations; that way, the Jira workflow can mirror how workitems behave in Azure DevOps.

For example, when starting an initial synchronization from Azure DevOps to Jira, the new Jira issue will follow the transition changes the workitem had.

If the Jira and ADO workflows are configured like this:

The workitem migration to Jira might fail even when all statuses are correctly mapped in TFS4JIRA, this is because the workitem historical transitions are like this:

According to the Jira workflow above, there isn’t an available transition from the ‘Open’ status to the ‘On Hold' status, so this workitem would be migrated to Jira to the incorrect status ‘Open’ instead of the 'In Review’ status.

To prevent this kind of error, global transitions should be added to each state of the Jira workflow.

 Related articles