2
1
0
2 answers
- 10-1
Seems it was a massive time delay ... took about 30min to trigger
Add your comment... - 210
Hi Charlie Schonken
Did you update the issue?
What happens is- Issue is updated
- Jira Cloud emits a webhook to the exalate app
- The exalate app checks if the issue is matching the trigger (and not yet under sync for that connection)
- The exalate triggers
As long as you don't touch the issue, there will be no sync happening.
Add your comment...
At the moment, when we need to sync from JIRA Cloud to Azure DevOPS, we use the Exalate buttons on the issue. This is a very manual process.
To overcome this, we have setup a trigger
The idea here is that only tickets that match the following conditions are automatically Exalated
Thus only tickets we mark to be sync'd will go through.
We updated one ticket to meet all these conditions and verified via JQL that this is the only one listed
But nothing happens. The ticket is not syncing.
Is there a time delay? Or something that would prevent it from Syncing?
Nothing in Sync logs
Nothing in Errors