Synchronization is handled by processors which are responsible for creating the messages sent to a destination instance, and processing incoming messages.
What's a processor
There are 4 different processor types in the synchronization process. Every processor has its own purpose.
The data filter processor prepares a replica which is sent to the remote instance.
|Input||issue||The issue you need to synchronize.|
|Output||replica||The replica which will be sent to the remote instance.|
A simple Data filter example
When the resulting replica is empty, then nothing is synchronized. Check the Unidirectional synchronization for more details.
You can set conditions in Data Filter as below:
Condition example: Don't send anything when priority is trivial
The create processor is executed only with the first synchronization request of an issue from the remote instance. Using the create processor, you must define the target project, issuetype, and summary.
Define the fields, you would like to receive from the remote side. You can also set your own values for any local issue field.
|Input||replica||The information sent from the originating instance.|
|Output||issue||An issue object which will be used to create the local issue.|
A simple Create processor example
If you don't specify the issue reporter in the create processor, the proxy user will be set as default reporter.
You can use script helpers in order to configure advanced conditions for your synchronization.
More advanced example
The change processor is executed when an incoming synchronization request is received for an already synced issue.
|Input||replica||The current information sent from the originating instance.|
|previous||The previous information sent from the originating instance.|
|Output||issue||An issue object which will be used to update the local node issue.|
A simple example of the synced issues update
The default configuration
By default, Exalate configures some basic scripts in the Sync Rules for your convenience.
Below is the default configuration of the Data Filter, Create Processor and Change Processor. It helps to synchronize an issue fields such as: assignee, reporter, summary, description, comments, resolution, status, attachments and project.
Send default data to the remote instance.
Default Data filter scripts
When the first synchronization request of an issue from the remote instance is received, create the issue in project TEST, issue type Task. Copy received summary, description, comments, and attachments.
Default Create Processor
Update local issue summary, description, add new comments and attachments and delete removed ones.
Default Change processor