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.   

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 JIra instances such that 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!

Jira to Jira Integration Use Cases (Basic to Advanced)

Work with simple syncs or customize all out with a Jira integration. 
The possibilities are only defined by you. 

Sync Any Default and Custom Field Data: Issues and Sprints

Sync all default and custom Jira issue fields like select lists, checkboxes, dates, versions,  etc. Maintain time tracking info with every sync. 

Map and sync issue types, reporters, assignees, labels, and statuses the way you want.

Create custom sync rules to orchestrate complex Jira workflows end-to-end. 

Sync Agile Fields in Jira & Maintain Issue Hierarchies

Synchronize epics and maintain the parent-child relationships along with the issue links between multiple Jira instances. 

entity.entityType == “Custom Object Name”

replica.customFields.”CF Name” = issue.customFields.”CF Name”

Advanced Comment Handling in Jira

Maintain the context of the Jira issue with advanced comment handling. Using comment helpers, modify the comment body and define your rules for syncing comments. 

Sync user mentions in comments between Jira cloud and Jira on-premise. 

if (replica.”TYPE” == “Case”) {
if(firstSync){
issue.projectKey = “UD”
issue.typeName = “Task”
syncHelper.syncBackAfterProcessing()
}
issue.summary = replica.summary
issue.description = replica.description
issue.comments = commentHelper.mergeComments(issue, replica)
issue.attachments = attachmentHelper.mergeAttachments(issue, replica)
}
else if (replica.”TYPE” == “Contact”) {
def contact = issue.”SF Contact”
if (contact == null || contact.trim() == “”) {
contact = “””||Name:| ||Title:| |||Email:| || | |”””
}
def name = replica.”Name”
def title = replica.”Title”
def email = replica.”Email”
issue.”SF Contact” = “””|| Name | $name |
|| Title | $title |
|| Email | $email|”””
}
else if (replica.”TYPE” == “Account”) {
def name = replica.”Name”
def description = replica.”Description”
issue.”SF Account” = “””|| Name | $name |
|| Description | $description|”””
}

Sync Jira Service Management Fields

Sync Organizations field in Jira Service Management. 

Map and sync the customer request type based on its mapping to the issue type. 

replica.comments = issue.comments.collect {
    comment ->
    def matcher  = comment.body =~ /\[~accountid:([\w:-]+)\]/
    def newCommentBody = comment.body
    matcher.each {
        target = nodeHelper.getUser(it[1])?.email
        newCommentBody = newCommentBody.replace(it[0],target)
    }
    comment.body = newCommentBody
    comment
}

Sync Components in Jira

Synchronize Jira issue components or create new ones depending on the information present on the remote Jira side. 

replica.comments = issue.comments.collect {
    comment ->
    def matcher  = comment.body =~ /\[~accountid:([\w:-]+)\]/
    def newCommentBody = comment.body
    matcher.each {
        target = nodeHelper.getUser(it[1])?.email
        newCommentBody = newCommentBody.replace(it[0],target)
    }
    comment.body = newCommentBody
    comment
}

Sync Third-party Plugin Data in Jira

Sync third-party plug-in data from Tempo worklogs, Insights, etc. 

Use ScriptRunner to automatically Exalate subtasks whenever a parent is Exalated.   

//Jira outgoing sync
issue.customFields.“Hobby”.value = replica.priority?.value ?: “Running” 
//Running will be set as a default option if Priority has no selected option

//Salesforce incoming sync
entity.SuppliedCompany = replica.customFields.“text”.value

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.