Note
Currently, you cannot sign-up to the community. We're fixing the issue. Sorry for the inconvenience. Please use AIDA (check below) for any queries.
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Hallo,
We are currently setting up a new sync. Both jira nodes are onpremise. We were ready to start syncing the sprints. We followed this guideline: https://docs.exalate.com/docs/jira-on-premise-d0267c9-how-to-sync-sprints "To start the synchronization of a sprint you need to create a trigger and select the sprint entity type. Sprints are synced after they are created or updated." We have set up the trigger accordingly. You can simply select sprint and the connection. We didn't activate the trigger, but we ran the bulk sync function for this trigger.
The problem afterwards is that all sprints of the Jira instance and not just those of the Jira Project stored in the connection run on a null pointer option. An attempt to fix this using bulk unexalate has no effect.
Likewise, commenting out the location for sprints in the outgoing script didn't help.
Since we don't necessarily need the sprint information at the destination, we would like to simply "solve" the sync errors.