When you start an issue synchronization, Exalate creates a replica. It's a copy of an issue which holds information that will be sent to the Destination side.
In the outgoing sync(data filter)
- replica variable defines the information added to the issue copy
- issue variable refers to the original issue
In the incoming sync(create and change processor)
- issue variable refers to the issue where the change needs to be applied.
- replica variable refers to the issue where the change happened.
To send issue summary field define replica.summary variable as belowTo apply received summary to the local issue, add the following sync rule into the incoming sync(create/change processor)
Another example is more complex and shows how you can use conditions to apply incoming data in different ways.
Sync Rules below are for the incoming sync in the local connection and have if blocks to handle everything in one create processor.
Check the local synchronization use case for more details.