| Term | Description |
|---|---|
Instance | An Instance is an issue tracker with the issues that you want to synchronize. |
Sync Rules | A set of rules that defines the synchronization behavior of the issue data. Exalate uses groovy scripting in its advanced sync rules. Sync Rules include 2 elements: Outgoing sync and Incoming sync. They are used to specify which data to send to the Destination Instance and how to handle incoming data from the remote instance. |
Connection | A Connection defines how issues are synchronized between instances. It includes information about two Instances and describes how they are related to each other. Each Connection has the following components:
|
Destination Instance | The Destination Instance is an Instance you want to set up a Connection with. |
Outgoing sync | Sync rules that specify which information can be transferred to the destination instance. Check the sync rules concept for more details. |
Incoming sync | Sync rules that define how to handle information received from the remote side. Check the sync rules concept fore more details. |
Trigger | A trigger starts the synchronization process. There are different types of triggers: |
Under Sync | An issue is under sync when data is synchronized with another issue tracker. |
Twin | A Twin is a pair of issues that are related to each other through a synchronization relation. Any modification is synchronized towards the other issue using the specifications of the relation. |
Replica | A Replica is a copy of an issue which is transferred to the other instance. You can specify what issue data you want to send to the other side in the Outgoing sync rules. |
Outgoing sync event | A synchronization event is a registration of the local issue's change. Exalate creates an outgoing sync event on the local issue update. |
Incoming sync event | A synchronization request is a registration of the remote issue's change. Every Outgoing Sync event on the sending side results in the incoming sync request on the Destination side. |
Proxy User | The Proxy User is the user account that will carry out changes such as creating issues, updating data, adding comments and attachments. More details |
Processors | There are 2 types of Processors:
These processors are specified in the context of the synchronization process. Sync rules are defined with the help of these processors. |
Filtering | Filtering allows limiting the information sent to other instances. |
Transformation | Transformation is the act of changing one type of value into another type of value. For instance, changing a status into a comment. |
Groovy | Groovy is a dynamic language for the Java platform. More details on this language: |
Destination instance URL | Link to the issue tracker you want to set up a connection with. |
