1
0
-1
1 answer
- 10-1
Hi Julie Metior
It seems the sync was blocked due to Azure node missing resources. It was resolved, but the issue was still in the queue.
The solution is to unexalate the issue or use clean-up tools, and exalate again.
If you connect it to the existing issue it should pick up the change and stop creating new issues.
Add your comment...
Hi,
We're syncing between ADO and JIRA DC.
We have experienced an issue today where -
Has anyone else experienced this and if so what do we need to do to ensure this doesn't happen again.
Thanks.