How to update a ticket "source" after being exalated

 
1
0
-1

I have a JSM (cloud) and a Jira server projects connected via Exalate.

At Exalating tickets from JSW, copies on JSM are created as expected.

However I need also to update the source issue on JSW with an info coming from JSM. The info is the key of the ticket in JSM.

I know such info is already available in the "remote issue" tab. However is not searchable in JSW so I need to highlight is in a specific customer field.

So far, the only way to update back the source issue is to force the synch by updating the JSM copy (using a fake comments or so).

I'm wondering if there's a way to trigger the synch back from JSM to JSW as a result of the first synch from JSW to JSM.

Thank you in advance, Pas

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Hi Serhiy,

      many thanks!

      I'm trying it right after and share the result with you.

      Regards, Pas

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Hello, Pasquale Scandurra thanks for posting on community.

        The solution should be the syncHelper.syncBackAfterProcessing() put into incoming sync of the JSM: 

        if (firstSync) {
  //...
  syncHelper.syncBackAfterProcessing()
}

        That should trigger a sync back from JSM to JSW as soon as the first sync is finished.
        Regards, Serhiy.

          CommentAdd your comment...