---
title: "Mapping one-to-many for States and Statuses"
canonical: "https://support.appfire.com/space/TSH/1800177080/Mapping%20one-to-many%20for%20States%20and%20Statuses"
format: markdown
---
The **TFS4JIRA Synchronizer** can synchronize multiple Jira status values to one TFS / Azure DevOps (formerly VSTS) state or multiple TFS / Azure DevOps (formerly VSTS) states to one Jira status. This gives more flexibility in the way states are handled. For example, you can map TFS / Azure DevOps (formerly VSTS) states `Done` and `Closed` to a single `Done` Jira status.

To map multiple TFS / Azure DevOps (formerly VSTS) states to one Jira state, first select a state in* TFS Values* listbox and then click *Add selected value* link (see screenshot below).

You can do the same in the opposite (TFS / Azure DevOps (formerly VSTS) to Jira) direction.

![image](media://e5260e9d-592c-4772-a9a2-ab9ffc1ccc26)

When multiple states are mapped, it is important to be able to determine what happens during the synchronization in the opposite direction - for example, if you map states `Closed` and `Done` in TFS / Azure DevOps (formerly VSTS) to `Done` in Jira, what is going to happen if you have TFS / VSST <span style="color: #333333">→</span> Jira synchronization enabled and there is a Jira issue to be synchronized with status `Done`? In this scenario, the* ***Default **state from the mapping of TFS / Azure DevOps (formerly VSTS) value is used (the default value is set in bold). You can select which value is set as default by clicking *set as default* link (see screenshot below)

![image](media://29e66a35-8240-4b12-8657-6b29b407d5c3)