With Backbone, you can define workflow mappings based on issue status, allowing you to define fine-grained distributed workflows between synchronized issues.
Are you on the right help page?
If you connect Jiras...
...via HTTP(S) (server/data center, cloud, local), you're in the right place.
...via email or file exchange (server/data center behind a firewall), check out this page instead.
This guide will demonstrate how to map a distributed workflow between two synchronized issues.
You should know both projects' workflow structure
You must assign your synchronization user the transition issues and administer projects JIRA permissions
Choose the correct workflow editor
Backbone includes two workflow mapping editors – the default (visual) editor and the advanced (text-based) editor. When you start configuring workflow mappings, it's important to choose the correct one for your needs.
Recommended use case
Lets you map workflow status between projects
All scenarios except when the advanced editor is recommended
Lets you map the workflow status, and also select specific transitions
Two scenarios only:
Let's create a workflow mapping with the default editor.
To get started, open the synchronization configuration and click Workflows > New workflow mapping;
If you see a different view (with two columns for the two projects), this means that you've already created workflow mappings for this project with the advanced editor – you won't be able to switch back to the simple editor without losing these.
Select which workflows you want to map, and what issue types you want to map the workflow for.
Now, you can use the editor to map what workflow state the partner project should be triggered to when your project sends them a certain workflow state:
In this example, when Project A sends Project B its current workflow status, Project B's workflow status will transfer to the same status.If there is more than one path between two statuses, Backbone will always select the shortest path. If there are multiple possible shortest paths, you can select which Backbone should take by clicking the path selection button:
On the next screen, map what workflow status your project should transition to when the partner project sends a workflow state. You can configure this in the same way as step 3.
The advanced editor lets you map workflow states between projects, and also select specific transitions between those states.
If you need to use the advanced editor, switch by clicking ... > Switch to advanced view:
If you want to create a workflow mapping for all issue types belonging to a project's default workflow, then click Default workflow mapping +.
If you want to create a workflow mapping for (a) specific issue type/s, click + New workflow mapping.
To define a workflow mapping, simply click + then you can define transition rules for your project. When you define a transition rule, you can define what transition for project's workflow should be triggered when the workflow status in the partner project changes. The condition is always a combination of the local status and the status of the partner project. Whenever the status in the partner project changes, Backbone will search for a matching condition and perform the selected transition (or transitions). The list of transitions to select depends on the selected local status.
Transition rule example
Here, if Project A is in status To Do, and Project B's workflow status changes to in Progress, then Project A's workflow status transitions to status In Progress.