This article describes how to synchronize the resolution field between Jira projects. There are two recommended methods of configuring this field:
- For when the resolution should be always be the same in both synchronized issues: Resolution passthrough mapping (transition)
- For when the resolution shouldn't always be the same in both synchronized issues: Resolution correlation mapping (transition)
This article explains how to configure both of these resolution field mappings.
Prerequisite: create a global looped workflow transition
Before you can configure the resolution field mapping, you firstly have to create a global looped workflow transition in the workflows being used by the projects that the resolution field is being synchronized to.
A global looped transition is a transition from any status to itself. It's necessary to create one because to change the resolution field, Jira must also trigger a workflow change – and if this workflow change is the global looped transition, then you can change the resolution without always having to transition to a new workflow state.
Create the global looped transition
- Define a new screen
- Assign the resolution field to it
- Create a new global looped transition for the workflow you are using in this project. Click to Workflows > Edit for the workflow you are using > Add transition > in the From status field, enter 'Any status' > In the To status field, enter 'Itself' > assign a name > assign the new screen from step 1 > click Add
- Get the ID of the global looped transition by clicking Text, then finding the global looped transition's name in the Transitions (id) column. The ID is in brackets next to the name – make a note of it
- Optionally, if you want to hide this new transition from your users:
- Assign your Backbone synchronization user to a group that only it belongs to
- Make the global looped transition only visible to users in that group by navigating to Workflows > Edit for the relevant workflow > click the global looped transition > Conditions > Add condition > select User Is In Group > select the group with only the Backbone synchronization user in it
Now, you can configure the resolution field mapping.
To always have the same resolution in both issues: Resolution Passthrough Mapping (Transition)
The Passthrough (Transition) setting always maps the same resolution between projects. You should only use this when both projects have the exact same resolution field values, otherwise you'll get an error.
To configure the mapping:
- In the Backbone resolution field mapping configuration, select Resolution Passthrough Mapping
- In the Transition ID field, enter the ID of the global looped transition (if you haven't got this set up, see the steps in the first part of this article) in the project's workflow:
- Click next, and do the same for the other project
Now, the same resolution value will be synced between projects.
When the resolution isn't always the same in both issues: Resolution Correlation Mapping (Transition)
The Resolution Correlation Mapping (Transition) setting lets you map certain resolution values in one project to certain resolution values in the other.
To configure this mapping:
- In the Backbone resolution field mapping configuration, select Resolution Correlation Mapping
- In the Resolution Mapping section, select which resolution should be mapped to which. The resolutions with the same numbers will be mapped, e.g. here, 'Declined' and 'Cannot Reproduce' will be mapped to 'Won't Do':
- Select a default resolution – this is the resolution that should be applied in case one certain resolution hasn't been mapped
- In the Transition ID field, enter the ID of the global looped transition in the relevant project's workflow (if you haven't got this set up, see the steps in the first part of this article)
- Click Next and enter the ID of the global looped transition in the relevant project's workflow
- Click Save