Contents
After you've set up a synchronization profile, you should see the results of TF4JIRA Synchronizer component working as TFS work items modifications that reflect corresponding Jira issues updates and vice versa. TFS4JIRA Synchronizer works according to the algorithm specified below.
Synchronization process
For every Jira issue, that has been modified since last successful synchronization run:
if the Jira issue isn't yet paired with any TFS / Azure DevOps (formerly VSTS) work item
- create a new TFS / Azure DevOps (formerly VSTS) work item
- copy values of the fields for which mappings are configured from the issue to the work item
- pair the issue with newly created work item
if the Jira issue is already paired with some TFS / Azure DevOps (formerly VSTS) work item
copy values of the fields for which mappings are configured from the issue to the work item
Analogical steps are applied for every TFS / Azure DevOps (formerly VSTS) work item, that has been modified since last run.
Please refer to the next section to find out how pairing Jira issues with TFS / Azure DevOps (formerly VSTS) work items is performed.
In case of a potential conflict (when both linked Jira issue and TFS / Azure DevOps (formerly VSTS) work item has been modified since last run) most recently modified item values are propagated.
How are issues and work items being paired?
Jira issue and TFS / Azure DevOps (formerly VSTS) work item pairing is being processed as follows:
- Jira issue custom field (selected in profile configuration as TFS Custom Field Name) value is set to TFS / Azure DevOps (formerly VSTS) work item id
- If Store Jira Issue Key in History profile option is not checked, TFS / Azure DevOps (formerly VSTS) work item custom field (selected in profile configuration as Jira Custom Field Name) value is set to Jira issue key. If Store Jira Issue Key in History option is checked, special comment containing Jira issue key is being added to TFS / Azure DevOps (formerly VSTS) work item
This page has no comments.