Flexible two-way sync
Real-time Jira Integration
Sync Jira Work Items (Issues) and Sprints between multiple Jira instances or between Jira and other platforms like ServiceNow, Azure DevOps, Salesforce, Zendesk, GitHub, and more.
Have your teams collaborate across different systems, departments, and companies in real-time.
- Free forever with the basic mode
- 30-day free trial for premium features
Opt for the no-code configuration. Or, customize the sync with the Script mode
Sync anything. From attachments to custom fields
& 40+ default fields
Get unlimited syncs, triggers, and connections
Available for Cloud & On-premise
Don’t share credentials with other teams.
Choose what info to share with other teams and just sync it.
Don’t copy-paste data between emails, messages, and issues.
Integrate your Jira with your partner’s system and see everything in one place.
click on image above to play full video
Don’t waste your time waiting on manual updates.
Automate your Jira sync and get real-time status updates.
Don’t switch between all the tools you use every day.
Stay in your favorite tool and sync the necessary data.
Sync Anything between Jira and Other Tools
Sync any entity using a one or two-way mapping. Configure and map the entities precisely as needed.
Jira
Jira Software (Cloud and Data Center)
Jira Service Management
Work Items (Issues)
(Bugs, Tasks, Stories…)
+40 fields are supported, including:
- Custom fields
- Summary
- Status
- Description
- Key
- Comment
- Attachment
- Priority
- Third-party plugin fields (e.g Insights)
Sprints
All fields are supported, incuding:
- Name
- State
- Start date
- End date
- Complete goal
- Origin board ID
- Goal
Jira Service Management
Tickets
+40 fields are supported, including:
- Custom fields
- Summary
- Status
- Description
- Key
- Comment
- Attachment
- Priority
- Reporter
- Third-party plugin fields (e.g Insights)
Sync Anything between Jira and Other Tools
You can sync any data available via API. The most common fields are listed below.
- Custom fields
- Summary
- Status
- Description
- Key
- Comment
- Attachment
- Priority
- Third-party plugin fields (e.g Insights)
- Name
- State
- Start date
- End date
- Complete goal
- Origin board ID
- Goal
Sync your jira with
Real-time Jira Sync
- Get real-time status updates on critical work items.
- Reduce manual data entry errors with automatic sync.
- Sync information uni or bi-directionally.
- Provide accurate and consistent information for the right stakeholders.
- Restart the sync automatically after down times.
Triggers for Automated Jira Integration
- Use native query language triggers for automatic information flow.
- Use fine-grained JQL triggers for syncing work items and sprints.
- Edit triggers anytime without disrupting the sync
- Have advanced independent control using triggers present on both sides.
Bulk Operations
- Sync multiple issues based on the conditions you set.
- Connect existing issues with remote entities.
- Have advanced control over bulk syncing.
- Choose to sync existing comments, attachments, or worklogs.
Custom Data Mapping Rules
- Create custom mappings with just a few lines of code (with Groovy scripts).
- Map statuses, issue types, and priorities the way you want.
- Handle formatting differences between Jira and other platforms.
- Control the sync between multiple Jira projects and instances.
- Fine-tune the data mapping independently for both outgoing and incoming information.
WHAT JIRA ADMINS SAY
"Exalates stands out the most due the fact that it is fully customizable. No use case is unsolvable. With other solutions, you're restricted to what they have configured for you."
"We have teams that need to work together, but in different systems. So instead or changing the way they work or making manual changes, we just sync with Exalate. They now stay in the tool they want, following company standards"
jorden van bogaert
atlassian service delivery manager
"Cut Service Desk costs by ~95%"
Senior PM
"Fully customizable — no use case is unsolvable."
Atlassian Solutions Expert
"We have 500+ tickets synced monthly"
Engineering Lead
“
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 |
Secure by Design
- Data isolation via single tenancy
- Encryption at rest and in transit
- Instant alerts for all data changes
- Automatic recovery from outages
- Secure sync with systems behind firewalls
- Granular filters to limit data exposure
“
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 |
01
install
02
connect
03
customize
04
automate
05
sync
The price of Exalate for Jira depends on the total number of users on your Jira and its deployment model. You can check the exact price on the Atlassian Marketplace.
System failures and down times lead to failed synchronizations. Exalate makes the whole sync process asynchronous using transactional sync queues at both integrating sides. It tracks sync events in the same order as the original issue event. So changes can be applied in the same order once the down time or error is fixed. It also has an integrated retry mechanism to resume the sync from the point of interruption without manual intervention.
Exalate handles formatting differences between different platforms through Groovy-based scripts. It provides a lot of Helper classes and methods to handle these different formats. For instance, it uses specific nodeHelper methods to take care of the HTML and markdown formats Azure DevOps and Jira supports.
Exalate is installed as an embedded add-on on Jira on-premise. For Jira Cloud, it works as an Atlassian connect add-on.
You can also choose to install Exalate on Jira via docker.
Access to these addons is via REST API requests, webhooks, iframes, etc depending on whether it’s Jira Cloud or on-premise.
Most cloud deployment models support multi-tenancy where infrastructure is shared to implement a certain functionality.
So there’s an increased risk of unauthorized access.
Exalate’s single-tenancy model ensures every instance has its own process space, file system, network and database completely separated from all other instances.
This model is available for all cloud deployments of Exalate like Jira, GitHub, Zendesk, Salesforce, ServiceNow and Azure DevOps.
Yes, you can integrate a Jira instance behind a firewall with a public facing Jira Cloud instance.
You can use the public-private connection type to do so.
You can also connect local project configurations by setting up Local connections such as between a JSM project and one or more Jira software projects.
More details on how it works can be found in the security and architecture whitepaper.
Exalate supports all standard fields in Jira Software, Jira Service Management, and Jira Work management, as well as Jira Align (with slight tweaks).
You can sync the basic issue fields like summary, description, issue types, comments, labels, attachments, priority, custom fields etc. In addition to these fields, Exalate’s advanced scripting engine allows you to sync any field that is available via REST APIs using the httpClient method.