Confluence has been updated to version 6.15.9

Expand all   Collapse all
Skip to end of metadata
Go to start of metadata

Introduction

You can synchronize Jira Server and Jira Data Center issues with other work management systems, supported by Exalate.

You can synchronize any two of the supported issue tracking platforms:

  • JIRA Cloud
  • JIRA on-premise
  • HP QC/ALM
  • Azure DevOps
  • GitHub
  • Zendesk 
  • ServiceNow 

Configuring Exalate for Jira on-premise

To configure Exalate for Jira on-premise:

1. Install Exalate.

Install Exalate from the marketplace and configure the proxy user.


Steps to install the Exalate app from the marketplace. 
  1. Log into your Jira instance as an admin.

  2. Click the admin drop-down and choose Add-ons. 

  3. Locate Exalate Issue Sync for Jira 2 Jira & more

  4. Click Free Trial to install the app. 
    We provide a free evaluation period for 30 days. The evaluation period can be extended twice until 90 days. 
    Check Licensing and pricing for more details.
  5. Accept terms and agreements. 
  6. You're all set! Get started to set up your first synchronization!


What's next?

Now you can proceed to the configuration and set up the connection.



By default, the proxy user is the user who installs Exalate.

To change the proxy user in the Navigate to General Settings → Proxy User in the Exalate admin menu to set the proxy user.

At the moment, there is a security vulnerability in Exalate, that lets you access private project data with the Connect operation. We recommend making sure, that the proxy user has access only to private projects.

For more info, check Security Vulnerability — You can access restricted project data with the Connect operation.

In Jira on-premise, the proxy user needs to have the following permissions:

  • Browse Project.
  • Create issue.
  • Edit issue.
  • Link issue.
  • Transition issue: change statuses (on issue transition).
  • If comments are synchronized, the proxy user will need to add, edit, and delete a comment.
  • If attachments are synchronized, the proxy user needs to add, and delete attachments.
  • If work logs are synchronized, the proxy user needs to add, edit, and delete work logs.
  • If security levels are synchronized, the proxy user needs to access the security levels.
  • If you're using trigger the proxy user must be able to search issues. 


Jira Service Desk permissions

The proxy user needs to be a service desk agent.


2. Set up a Connection.

Exalate syncs your data through connections between two instances, or locally within the same instance. You can establish a public, private, or local connection.

In Exalate for Jira on-premise, there are three configuration types of connections:

  • Basic—a connection that allows synchronizing a basic set of issue fields. Recommended for use cases of basic complexity.
  • Visual—a connection between instances is established using a single visual interface. Requires admin access to both instances. Recommended for use cases of basic to intermediate complexity.
  • Script—each side of the connection is set up separately with groovy-based script sync rules. Recommended for more complex and advanced use cases.


Depending on the license plan different configuration types are available. Check Pricing and licensing for more details. 


Basic connections

Check out how to set up a Basic connection in Set up a Basic connection in Exalate for Jira on-premise.

Visual connections

Check out how to set up a Visual connection in Set up a Visual connection in Exalate for Jira on-premise.

Script connections

Check out how to set up a Script connection in Set up a Script connection in Exalate for Jira on-premise.


3. Synchronize an Issue.

Go to an issue and use the Exalate operation to start synchronization.

Find out more ways to synchronize issues automatically.


Read about issue sync in Jira On-premise configuration guides.