The Exalate team will be on holiday for the coming days - returning Jan 4 Enjoy & stay safe
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
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:
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.
Hello, alex pirka have you tried approach described here: Avoid updating issue with older changes ADO <> Jira ?
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
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
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.