Transition equivalence is the equality of a transition in one project workflow to a different transition in a different project workflow. This makes it possible to run a transition for one project in a batch of projects and have it run transitions in other projects within the batch even if the transitions don’t have the same name.
For example, consider a batch of three projects. The next and final transition of the first project is named Release and completes the workflow. The final transition of the other two projects is named Issue, but the Issue transition is not the next transition in their workflows. Also assume that a system administrator has defined the first project’s Release transition to be equivalent to the other project’s Issue transition. After the first project’s Release transition has been run, the other two project’s Issue transitions will run as well, completing the workflows of all three projects in one step.
A system administrator can define transition equivalence between:
Transition equivalence can cause seemingly inexplicable changes in a project’s workflow. Consult a system administrator for more information on the transition equivalence configured for project definitions in your vault.