two-way integration

Jira to Jira Integration

Set up a one-way or two-way Jira to Jira integration. Sync Jira issues, and sprints between multiple Jira instances. 

Experience Jira Service Management integration with other Jira instances and get real-time status updates. Break down team silos and move data around however you like.   

        3.5/4 highest rated on the Atlassian Marketplace

sync issue types, labels, priority, status...

sync any custom fields, attachments... 

sync comments, worklogs, history...

sync issue types, labels, priority, status...

sync any custom fields, attachments... 

sync comments, worklogs, history...

2000px-Dell_Logo.svg-e1507283755907

Jira Sync: Real-time, Secure Data Flow

Keep your development, support, or operations teams aligned with instant status updates. With the right Jira sync, you will have secure collaborations across multiple systems, no matter where your teams are located. 

Increase productivity with real-time Jira issue sync. Eliminate delays and ensure everyone has access to the latest info.

Empower teams to work more efficiently and focus on what they do the best.

Ensure accurate information flows securely between multiple Jira instances.

Tailor the integration to match your specific needs, from issue types to custom fields, ensure a smooth fit into your processes.

Make informed decisions with access to consolidated data.

Convert customer tickets in Jira service management into actionable Jira issues with ease.

Connect Multiple Jira instances, Anyway You Want!

Sync standard and custom Jira issue fields exactly the way you need between your Jira instances. Map Jira issue fields in the sync rules to fit your specific workflows. Define precisely which data should be synced, how often, and under what conditions.

 

Check the full list of supported fields for Jira

Its hard to talk about supported fields, because with Exalate you can support a lot. And it is impossible to capture on a single page. We have done cases with very weird things - certainly not limited to the ones listed on the documentation.

discover if we cover your integration requirements
book a demo

Book a demo to see Exalate in action

 

Get the Most out of Your Jira to Jira Integration

Choose the direction of your Jira sync. Connect Jira cloud with Jira on-premise by installing the app right from within your environment. 

Experience automatic, real-time Jira sync that keeps your data up-to-date across all your instances. Use Jira Query Language to set up granular triggers at each side. 

Sync historical Jira issue data with Exalate’s bulk operations. Connect multiple existing issues using Bulk Connect. Start syncing issues automatically with the same trigger specifications using Bulk Exalate.

Use Groovy-based scripts to create custom sync rules in Jira. Set advanced mappings, use conditional logic, and much more for a truly flexible Jira integration. Use our AI to generate your sync scripts.

Test your connection, view the issue sync status or connect existing issues with an embedded Exalate interface in Jira. Always have the latest information within your Jira environment.  

Decentralized Integration

Retain independent control of your integration, even in cross-company scenarios. Don’t worry about how adjustments made on one side will impact your existing configuration. There's no requirement to share credentials or administrative privileges, eliminating the risk of exposing sensitive data.

Sustainable Scalability

Begin with pre-configured connections for simple sync needs, then expand and accelerate your growth by employing custom script-based connections. Connect with your integration partners to foster better relationships.

Top-notch Security

Protect your sensitive data from unauthorized access with our single-tenant architecture. Stay ahead of any data breach or suspicious activity using advanced endpoint detection and response (EDR).

The advantage of Exalate’s decentralized architecture is that it’s not like a new learning curve for the customers to get into a new platform and figure out how they need to operate. They can just operate as they normally do, and that makes a huge impact on the overall outcome of security incidents.

Alexander Sinno |

logo_nviso

Get Started In Minutes

01

install

Install the Exalate app on all the tools you want to sync. This way, every admin has complete control over their integration.

02

connect

Use the instance URL to connect the instances you want to integrate. Choose the no-code set-up or the Script Mode.

03

customize

Configure your sync rules to make sure the right data is shared. Automate your sync with triggers.

04

synchronize

Now your instances are connected and will automatically exchange information instantly. Happy syncing!

Sync Simple or Go Advanced

Start with simple Jira to Jira integrations or customize the sync to handle any use case.

Sync Sprints and Epics

Bi-directionally sync Sprints and Epics between Jira instances. Keep sprint details, epic progress, and related issues aligned across teams, maintaining consistency and visibility in cross-instance projects.

In practice:

Epic.receive()

//sync sprints

def boardIds = [“50”, “80”, “130”, “144”] //Boards which sprints will get synced

if(entityType == “sprint” && boardIds.find{it == sprint.originBoardId}){

replica.name = sprint.name
replica.goal = sprint.goal
replica.state = sprint.state
replica.startDate = sprint.startDate
replica.endDate = sprint.endDate
 replica.originBoardId = sprint.originBoardId

}

if(entityType == “issue”){

   //Executed when syncing an issue to a remote side

replica.summary = issue.summary
replica.description = issue.description
replica.project = issue.project
replica.type = issue.type

//sprint….

replica.customFields.Sprint = issue.customFields.Sprint

}

Sync Multiple Projects with Multiple Issue Types

Sync certain issue types into specific projects depending on the conditions you set. 

In practice:

if(replica.type.name == “Bug”) {
2 issue.projectKey = “TESTERS”
3 issue.typeName = “Test”
4 }
5 else{
6 issue.projectKey = “DEVELOPERS”
7 issue.typeName = “Task”
8 }

Connect Jira Service Management with Jira Software

Sync only public comments between Jira Service Management and Jira. Tag the right person by passing user mentions in the comments.

In practice:

issue.comments = commentHelper.mergeComments(issue, replica, {it.internal = true})

Automate Outsourced Dev Workflows

Enable controlled ticket sharing between an internal Jira and an external development firm’s Jira ensures full ownership of project records. Sync statuses for real-time visibility

In practice:

def statusMap = [
“remote status name”: “local status name”
]Go to Entity Sync Status, put in the entity key, and it will show you where to find the remote replica
by clicking on Show remote replica.
 def statusMap = [
 “New”   : “Open”,
 “Done”  : “Resolved
 ]

def remoteStatusName = replica.status.name
issue.setStatus(statusMap[remoteStatusName] ?: remoteStatusName)

Sync Third-party Plugin Fields in Jira

Sync third-party app data like tempo worklogs, insight fields, etc. 

Never lose sight of information.

In practice:

replica.workLogs = issue.workLogs
TempoWorkLogSync.send(
 “dJWtvBhJUkoHroDcEd8iYyYfnd0Bm”,  // replace the “token” with the //previously generated access token
replica,
issue,
httpClient,
nodeHelper
)

We can now handle around 500 customer incidents per week, thanks to Exalate, which is a very good result regarding the number of products we’re dealing with. It synchronizes 45x faster than our previous solution.

Christof Cuyper |

GANTNER_Logo
Start Synchronizing Your Tools​

The team was very hands-on and very responsive. If we encountered an issue, they were able to resolve it quite fast.

Maarten Cautreels |

Always Ready to Help

Get the best assistance from technical support managers and engineers. Go at your own pace or lay back while we do most of the work for you.

FAQ

Answers to the most frequently asked questions

You can sync any Jira issue and sprint data. Sync all custom fields like select lists, cascading select lists, checkboxes, and much more. Additionally, you can also sync epics and sub tasks between multiple Jira instances. You can set up advanced comment handling like syncing user mentions in comment threads or impersonating comments. 

Plus, sync third-party plugin data from Tempo Worklogs, Insights, etc. 

The possibilities are endless. Get the entire list here. 

Exalate offers a no-cost Basic mode for straightforward synchronization use cases, giving you 1,000 free syncs per month. To access the advanced Script Mode, you’ll need to purchase the Premium plan following a complimentary 30-day trial. You can find Exalate for Jira  on the Atlassian marketplace.

You can use Exalate with Jira Cloud or on-premise. You can also install it via docker for additional security needs. You can even connect Exalate with an instance behind a firewall, called private connections. 

We provide both Standard and Premier Support options. Standard Support covers help with specific issues related to installation, upgrades, troubleshooting, and similar concerns. Premium Support assigns you a dedicated support engineer, aids with your configurations, offers enhanced SLAs, and more. Additionally, we offer a specialized Exalate for Service Providers package to facilitate connections with your service providers and foster a robust collaborative network.

Yes, Exalate supports single-tenancy, which minimizes the risk of information exposure at the infrastructure level. When you deploy an Exalate Cloud node, it functions within a ‘Kubernetes pod’ meticulously configured to safeguard against data leakage.

Yes, you can use Exalate to connect multiple Jira instances. Exalate also supports other popular tools like Azure DevOps, Zendesk, GitHub, etc. You can also set up a connected network with your external partners through the MSP program Exalate offers. 

Exalate is available for all Jira products like Jira Work Management, Jira Software, Jira Service Management, etc. Depending on the type of your product, additional customization might be required.