This article describes the concept of the synchronization use case, where both sides are private Jira on-premises.
Concept
Exalate handles private-to-private use cases with the help of an intermediate public Jira instance. The public instance is used to transfer data received from one private Jira instance to another private Jira instance.
Basically this public Jira is an intermediate connector between private sides.
Pre-requisites
- Private Jira A
- Private Jira B
- Public Jira AB
Set up the connection between the private and public Jira instances(A to AB) and then set up another connection between the public Jira and another private Jira(AB to B).
Such configuration is applicable for the following use cases:
- Both JIRA instances are not available from the public network (are behind a firewall)
- You want to share with the other side only some limited set of data
- You don't want to base the configuration on email or file exchanges
- You are working on projects where the main focus is on security and privacy
Configuration Steps Overview
- Set up a connection between the private Jira a and the connector public Jira AB.
- Set up a connection between the connector public Jira AB and the other private Jira B.
For more information, please read the getting started guide for Exalate for Jira on-premise.
Limitations
- Syncing one issue using multiple connections is available only on Exalate for Jira on-premise. Therefore, only Jira on-premise can be used as an intermediate public connector.
- Some delay is possible as far as private-public connection works by polling data from the public side
- Different connections to sync multiple projects with multiple issue types might affect Exalate performance.
We recommend configuring one connection on every instance with conditional blocks to improve the performance.
Example:
- Jira A connection: A to AB;
- Jira AB connection: A to AB and AB to B;
- Jira B connection: AB to B