In Server <> Cloud scenarios, some changes from cloud are not synchronized to server

Description

Steps to reproduce

  • Create an integration between server and cloud

  • create an issue (on server)

  • stop the integration

  • transition to "in progress", then to "done" (on cloud)

  • start the integration

Expected behaviour
The tickets should both be in status "done".

Current behaviour
The tickets are in different states "in progress" (server) and "done" (cloud).

Interim analysis result
Some time ago, the Jira Cloud changed the order how entries in the issue history are returned. Now they are no longer returned in the order "oldest first", but "latest first". Therefore Backbone stops checking for changes too fast.

Environment

None

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

Participants

None

QA Status

None

Deployment

None

Documentation Status

None

UI Concept

None

External Votes

None

Time tracking

4h

Sprint

None

Fix versions

Priority

Major
Configure