Azure is more restrictive than Jira when it comes to linking between work items , thus and it’s not always possible to synchronize some links from Jira to Azure. We synchronize
Handling such restrictions TFS4JIRA synchronizes links in a sorted manner (starting , starting with those having smaller ID )number.
This behaviour means that when two links cannot exist with each other on the same work item in Azure we are only going to synchronize one with a lower id.
Example
opposite links in Jira are allowed to point to the same work item from one work item (for instance in default Jira configuration, A can be blocked by B and A can blocks B).
Example:
Jira allows issues to co-dependently block each other - issue A can be blocked by issue B, blocking B at the same time:
(A blocked by B and A blocks B). Since Azure does not allow such behavior for opposite links thus only the links relation, the app will only synchronize link with the lower id is synchronizedID.