How to update a ticket "source" after being exalated

General Questions
, , ,
1

Originally asked by Pasquale Scandurra on 20 December 2022 (original question)

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

2

Answer by Pasquale Scandurra on 21 December 2022

Hi Serhiy,

many thanks!

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

Regards, Pas

3

Answer by Serhiy Onyshchenko on 21 December 2022

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.