1
0
-1

Hi, we are setting up an issue sync between 2 Jira Cloud instances in which we want to sync assignee comments and history items (= issue attribute updates) from the (3rd line) replica issue to the (2nd line) original JIRA issue as new COMMENTS in the original issue, which the customer can see in his/her service request in the (1st line) Jira SM portal. We want to sync history items of the replica issue as comments because we do not want to affect the original issue attributes and history items in the 2nd line Jira Cloud project, while informing the customer about what the 3rd line team is doing.

For this purpose we made Groovy scripts for the issue sync, history item to comment copy and new comment sync. However, what we encounter is that newly added user comments are synced, but syncing the latest history item of the replica issue as a new comment for the original issue results in a stack trace in the scripting console and fails. We cannot pinpoint what is causing this sync issue.

So I am looking for pointers on how to resolve this history item sync issue. Do you have any examples/example scripts on how this can be done, which could allow us to pinpoint the scripting error?

Any pointers to be able to debug this sync issue are appreciated

Thanks in advance

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      It might be more useful to sync change history into a text field, as showed here:

      https://docs.idalko.com/exalate/x/AgCqBQ

        CommentAdd your comment...