---
title: "Map Jira Resolution when using Azure DevOps Scrum process template"
canonical: "https://support.appfire.com/space/TSH/1800766649/Map%20Jira%20Resolution%20when%20using%20Azure%20DevOps%20Scrum%20process%20template"
format: markdown
---
# Prerequisites
- [Customize Jira to allow Resolution mapping](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800669276)
- [Change Reason and ResolvedReason during State transition](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800275482)
# Overview
Scrum default process template in Azure DevOps only has `Reason` field for all known item types. State `Done` in Azure has only one Reason value `Work finished`. State `Removed` has one universal state `Removed from the backlog` for each known item type except `Bug`. It is enough to set up a single sync profile to handle all work item types.
If you would like to use `Not a Bug`, `Duplicate` resolutions for Bug (or for other work item types), enable resolution screen as described in [Customize Jira to allow Resolution mapping](https://appfire.atlassian.net/wiki/spaces/TSH/pages/1800669276)
If screen is not enabled a warning in logs during transition to final state will appear:
```
WARN SpartezSoftware.Synchronizer.Services.JiraIssueTransitionerService - Jira’s issue does not contain 'resolution' field. It could have been hidden from Jira screens.
```
# How
## Workflow mapping
Recommended workflow mapping for three statuses in Jira while having seven in Azure (all states below `Done` and `Removed` can be set by preferences, statuses `Done` ↔︎ `Done/Removed` is recommended for this guide)
## Resolution field mapping
Having above workflow mapping we can set mapping for `Resolution` **<-** `Reason` field mapping. Please notice this mapping **unidirectional**. In Jira we have one `Done` status which maps to `Done` state in Azure. There is only one `Reason` for marking work item as `Done` in Azure - `Work finished`. Anything else is forbidden in default Scrum process.
From Azure to Jira it is possible to map different resolution field being agnostic to state and status. If state is moved to `Removed` or `Done` in Azure it is transforming Jira issue to status `Done`. And depending on the Reason we can set different resolution thanks to mapping like below
> Macro (attachments)