Confluence has been updated to version 6.15.9

This article describes one of the main Exalate concepts - Connection.


Connection defines how issues are synchronized.  

It includes information about the instances you are syncing, describes how these instances are related to each other, and how the information is mapped.

For example, you can define a connection between a project with tasks to track a system's deployment on one side, and another project which tracks bugs and feature requests on the other side.

Each connection has the following components:

  • Connection type - defines how to communicate with the remote instance. Exalate provides the following connection types:
    • Local connection
      Allows synchronization of data between projects within the same instance.
    • Public
      Allows synchronization of data with an instance, which you can access from your side and is available in a public network.
    • Private
      Allows synchronization of data with an instance, which is behind the firewall and you cannot access it from the public network.
      Check private/public issue synchronization for more details.
  • Information about the Destination Instance
  • Sync Rules - defines the behavior of synchronization
  • Scope - defines synchronization context: what issues to sync and how to start the synchronization process

Connection statuses

  • Pending
    The connection is pending, waiting for acceptance from the other side.
  • Active
    A connection has been established and synchronization messages start to go out. You can now synchronize issues.
  • Deactivated
    Synchronization is paused, but changes are queued for a later update. Once you activate the connection, all changes will be applied.

Configuration overview

You can either initiate a connection or accept an invitation from the person who's started the connection setup on the other side. 

For local connections, you don't need to send any invitations.

To keep it simple, imagine you're trying to set up a connection between Jira instances that are available in a public network.

Connection set up steps are the following:

  1. Initiate connection
    1. Provide a destination URL
    2. Choose the configuration type
    3. Specify connection information  
    4. Select a project where you want to create issues received from the other side
    5. Initiate a connection
  2. Send invitation
  3. Accept the invitation on the other side
    1. Select a project where you want to create issues received from the other side
  4. Configure sync rules

The connection name is limited to 255 characters for all the work management systems except for Jira, where you can configure the desired value for string length.

For more details check out our getting started guide