This article shows how to synchronize sprints in Exalate for Jira on-premise.
You need to sync sprints with a trigger before syncing issues.
Starting from version 4.7.0, you can add sync rules to synchronize sprint data. Exalate considers issues and sprints as independent entities.
The scripts below use board IDs to identify what sprints to sync. For example, if you enter a Board ID
1, you will sync all sprints from that board.
Sprint synchronization in Jira on-premise is available only for Script connections.
Use the following script to send the sprint data:
Use this script to sync the received sprint data on your side:
You can control which sprints get synchronized from the outgoing sync rules.
When you don't want an entity to be synchronized, use return before actually setting any value on the replica.
Fields of the sprint entity
How to start sprint sync?
To start the synchronization of a sprint you need to create a trigger and select the sprint entity type. Sprints will be synced after they are created or updated.