Workflow Mappings

With Backbone, you can define workflow mappings based on issue status, allowing you to define fine-grained distributed workflows between synchronized issues.

This guide will demonstrate how to map a distributed workflow between two synchronized issues.

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.

Name

Functionality

Recommended use case

Default editor

Lets you map workflow status between projects

All scenarios except when the advanced editor is recommended

Advanced editor

Lets you map the workflow status, and also select specific transitions

Two scenarios only:

If you have already configured workflow mappings for a project in Backbone versions 3.3 or earlier, and you don't want to lose them. This is because these earlier versions only used the advanced editor – and you cannot switch back to the default editor in a project without losing workflows created in the advanced editor.
There are certain transitions in your workflows that can be executed in multiple ways, and you need to define which exact path should be taken. This is because you can't select which transitions between states should be made in the default editor.

Default editor

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.

Advanced editor

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.