TFS4JIRA - I want to synchronize new items one-way only, but keep bi-directional synchronization on previously synchronized ones
- Michał Szymul
- Christie Gera
Overview
Use case: As a TFS4JIRA user, I want to ensure that issues created in my Jira instance are synchronized to Azure DevOps (or otherwise). I do not want any new work items created in Azure DevOps to be synchronized to Jira. However, if an Azure DevOps user updates a work item that was previously migrated from Jira, I want these changes to be synchronized.
This solution works both for TFS4JIRA Cloud Native and self-hosted.
On this page: |
Step-by-step guide
Set the general synchronization mode to Both directions.
Make sure that in the Fields section of the synchronization profile setup, you have a mapping for Labels ↔︎ Tags
Create a label/tag that can be used in a synchronization filter and can be added to a Jira issue (for example, a “sync” label).
Go to Filter settings in your synchronization profile in TFS4JIRA, enable Filter Azure items (Cloud native) / Filter TFS items (self-hosted), and add the following WIQL query: [System.Tags] contains 'sync'.
With a setup like this one, the synchronizer will synchronize every issue available in the Jira project to Azure DevOps. However, in ADO, the synchronizer will look only for work items that have the “sync” tag (which can either be added in ADO after the synchronization or synchronized from the Jira “label” field thanks to the mapping created with this instruction). Any work items without this tag will be ignored. Naturally, you can add additional factors to the filter if you want to narrow down the items eligible for synchronization even further.