How to deal with concurrency in bidirectional sync?

Originally asked by alex pirka on 13 June 2022 (original question)


Hi,

we figured out following issue within an internal project connection, synchronizing one project to another in the same Jira servicemanagement instance

IS:

Pre Sync

Project A → Ticket 1 → Field Y is empty

Project B → Ticket 1 → Field Y is empty

Both Tickets are linked via Exalate Connection.

Sequential Ticket editing

  1. Project A → Field Y is set and starts a synchronisation
  2. Project B → Comment Field is filled and starts a synchronisation

Post Sync

Project A → Ticket 1 → Field Y is empty, comment is filled

Project B → Ticket 1 → Field Y is empty, comment is filled

Should:

Pre Sync

Project A → Ticket 1 → Field Y is empty

Project B → Ticket 1 → Field Y is empty

Both Tickets are linked via Exalate Connection.

Sequential Ticket editing

  1. Project A → Field Y is set and starts a synchronisation
  2. Project B → Comment Field is filled and starts a synchronisation

Post Sync

Project A → Ticket 1 → Field Y is filled, comment is filled

Project B → Ticket 1 → Field Y is filled, comment is filled

Synchronisation Operations should be executed sequentially.


Answer by Serhiy Onyshchenko on 13 June 2022

Hello, alex pirka
have you tried approach described here: Avoid updating issue with older changes ADO <> Jira (old community) ?