Customers can configure validators or conditions in their workflow transitions; these can restrict which users and when can users transition from one status to another. TFS4JIRA will follow all the rules implemented in Jira and this can be an issue for the synchronization process, especially if there are no global transitions configured in the workflow.
Global transitions allow users to go and come from any status of the workflow. This is also how workitems in Azure work, so if the transition performed in Azure is not available in Jira this will throw errors in the synchronization.
For example, this Jira workflow doesn’t have global transitions, so if the user transitions from the final state to the initial state in Azure, this will throw errors because in Jira a transition from the Closed status to the Open status doesn’t exist.
Jira Workflow:
Azure Workflow:
To prevent this kind of error, and to avoid asking the customer to change their current restrictive configuration, the customer should add global transitions to the Jira workflow and these transitions must have a condition that only allows the TFS4JIRA add-on to use it (and see it). That way the synchronization process won’t be affected by the validators/ conditions added in the common transitions and also Jira users can follow the rules implemented in their workflow.
Jira Workflow:
Azure Workflow:
