Applies This article applies to:
TFS4JIRA Cloud
...
TFS4JIRA Self-hosted
...
Overview
TFS4JIRA lets you map fields in the profile configuration, you are able to map multiple fields on one side to one field on the other, like in this example:
...
However, there is a specific logic behind the synchronization of the values when fields are mapped this way. multiple fields to a single field. In the Mapped Fields example below, Azure DevOp’s Description and Acceptance Criteria fields are both mapped to Jira’s Description field:
...
What happens when multiple fields are mapped to a single field?
In the example above, Azure’s “Description” and “Acceptance Criteria” the Description and Acceptance Criteria fields from Azure DevOps are mapped to “Description” the Description field in Jira. We use The mapping has the following characteristics:
There is a one-way synchronization from Azure
...
DevOps to Jira, indicated by the single-direction arrow.
The Description field in Azure DevOps is the primary field.
With this setup, an Azure Work Item with a Description field will have it’s value the value in the Azure DevOps Description field is synchronized with the Description field in Jira. However, if the work item in Azure DevOps uses the Acceptance Criteria field, it’s its value will not be migrated mapped as Jira’s Description. This is because only the “Primary” Primary field in a field multi-mapping scenario has read/write permissions, while all others . All other fields only have write permissions.
The example above shows a illustrates one-way synchronization. With bi-directional synchronization enabled, the mapping would look like thisdisplays as:
Jira Azure
Description ↔︎ Description (Primary)
→ Acceptance Criteria
In the above bi-directional setup, synchronization from Azure → DevOps to Jira would work works the same as the original, one-way synchronization example. However, while synchronizing from Jira → to Azure DevOps, the synchronizer first checks if the Description field is available for the target work item type. If not, it will look looks for the Acceptance Criteria field and put adds the Jira Description value there.Our recommendations
Recommendations
The most reliable synchronization solution for synchronization is to always have define a unique link for each field instead of using the multi-mapping feature. .
However, if you cannot add new fields in either Jira or Azure DevOps, we recommend setting up configuring a separate profile to synchronize that each Issue /and Work Item type.
For example, Acceptance Criteria is are usually specific to “Bug” the Bug work item type in Azure DevOps. You can copy Copy your existing synchronization profile and use it for Bug synchronization only. Therefore, you will be able to map Jira’s Description only to Azure’s Azure DevOp’s Acceptance Criteria.