Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Hi Team,
I have tried to sync the destination key back to source issue with below codes, but it seems it sync back some other fields also. please help on how to sync only back destination key while first sync.
Incoming sync (destination side)
1
2
3
if
(firstSync){
syncHelper.syncBackAfterProcessing()
}
Incoming sync (source side)
1
issue.customFields.
"remote issue key"
.value = replica.key
Regards,
Moogambigai G R
I have added incoming destination and source side.
Here I get the destination key in "OEM Sync ID" text field.
Hi there,
Is there any update on my question?
Regards,
Moogambigai G R
Hi there,
Is there any update on my question?
Regards,
Moogambigai G R
Hi There,
Is there any update?
Regards,
Moogambigai G R
Hi, I can see on your incoming script that there are lot fields being impacted and it is expected to see changes on it.
For example:
I have tried the following on my two cloud instances and worked.
Incoming sync (destination side)
if
(firstSync){
syncHelper.syncBackAfterProcessing()
}
Incoming sync (source side)
issue.customFields.
"remote issue key"
.value = replica.key
Would you be able to clarify your use case?
Hi Andres,
We are sync two projects in same instance, its a two way sync.
Whenever Project A is synced to Project B, destination project B key should show in one of the customfield in Project A or in Project A JQL result