Issue loop back creating duplicate issue when attachments aren't synced over in the initial sync exchange

 
1
0
-1

Hi,


We're syncing between ADO and JIRA DC.


We have experienced an issue today where -

  • an issue was entered in JIRA, with 2 attachments associated with it
  • the issue was added to the sync queue and thereafter was blocked with the following error message

               

  • HOWEVER, despite being blocked, the defect text synced anyway, the attachments didn't
  • AND THEN, because the defect didn't sync in it's entirety, ADO saw it as a newly entered ADO issue, rather than an incoming JIRA issue
  • Which led to the issue syncing back to JIRA as if it was a newly entered defect in ADO, basically looping back creating a duplicate issue in the process.


Has anyone else experienced this and if so what do we need to do to ensure this doesn't happen again.



Thanks.

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -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.


        CommentAdd your comment...