Azure DevOps as the Source of Truth(in case of conflict) in a Jira DC ↔ Azure DevOps Private/Public Connection

General Questions
1

Hello Exalate Team,

I am integrating Jira Data Center and Azure DevOps using Exalate through a Private/Public connection.

One of the key requirements is around conflict management and data ownership.

Use Case

  • Jira DC and Azure DevOps are synchronized bidirectionally.
  • Azure DevOps should be considered the master system and the source of truth.
  • In situations where the same field is updated on both sides before synchronization completes, we want Azure DevOps values to take precedence.
  • Ideally, any conflicting changes coming from Jira should either:
    • be ignored, or
    • be overwritten by the Azure DevOps value during synchronization.

Questions

  1. Is it technically possible to configure Exalate so that Azure DevOps always wins during conflicts?
  2. If yes, what is the recommended approach?
    • Incoming sync rules?
    • Unidirectional field ownership?
    • Conditional synchronization logic?
    • Conflict detection using timestamps?
  3. Are there any best practices or examples for implementing a master/slave (source-of-truth) model in a Jira DC ↔ Azure DevOps integration?
  4. Does the fact that this is a Private/Public connection have any impact on conflict resolution behavior?

Thanks, Dhiren