The challenge is as follows
In order to give a comprehensive answer, I compared how three of the issue sync solutions with the most active installations support nfeed field synchronization in general:
Here are the results of my analysis:
nFeed field to nFeed field (same nfeed keys)
You can configure this in the corresponding script fields by adding the following lines
replica.customFields."nfeed field" = issue.customFields."nfeed field"
issue.customFields."nfeed field" = replica.customFields."nfeed field"
If you know how the other sync solutions handle these cases, please comment here, and I am happy to edit my answer.
With exalate you can create a script which retrieves the nfeed information through REST on one side, transport it over the wire to the other JIRA, and lookup the corresponding value in the database table.
Check following example which provides the details of this approach
How to sync nfeed fields when key values are different
It is an example of the integration flexibility of Exalate
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs