Querying all issues in updated order from a given point forward

[Jens Bjerre]

We have a need to quickly get all issues that are created/changed synchronized into a second system, but the REST API does not expose any symptotically increasing number that can be queried on, and no we cannot use the updated timestamp as the resolution is way too low and modern machines can make a huge number of changes in that time, not to mention the pagination issue causing issues.

I know that this number exists in the database as we used it in the Server version, it was called something like change_group_id, but that is not available in the REST interface.

We cannot use the webhook method either as it is too unreliable as anything from service restarts to network issues can mess with it.

Is there some way of being able to reliably resume a synchronization operation from some point? 

[Shawn Doyle - ReleaseTEAM]

Hi @Jens Bjerre 

A marketplace app may be the quicker approach here, there are 3 marketplace partners that make a backup tool that could be used for replication, all start with the letter "R".

[Jens Bjerre]

Thanks, but this is not replication, we use the state changes of jira issues in a secondary system that has its own workflows, we don't need a backup solution, we need what webhooks provide just pulling rather than pushing.