sync issue types, labels, priority, status...
sync any custom fields, attachments...
sync comments, worklogs, history...
sync opportunity, case, taks, account, product...
sync owner, status, number, priority...
sync contact details, internal comments...
Start for free
Increase productivity and eliminate the need for manual data entry and redundant tasks.
Keep your team focused on core competencies – selling and developing products.
Understand the impact of feature requests on your sales pipeline or other insights.
Get a 360-degree view of your customer interactions.
Make informed decisions backed by consolidated data.
Tailor the integration to your unique business processes.
Convert Salesforce cases or opportunities into actionable Jira tasks with ease.
Sync Any Data Between Jira and Salesforce
Map standard and custom Salesforce objects any way you want with Jira work items.
Use sync rules to define which data should be synced in your Salesforce to Jira integration.
Salesforce
Case
All fields are supported, including:
- Custom fields
- Account Name
- Asset
- Business Hours
- Case Owner
- Contact Email
- Escalated
- Priority
- Product
- SLA Violantion
- Type
Problems
All fields are supported, including:
- Close Date
- Contract
- Delivery/Installation Status
- Description
- Lead Source
- Order Number
- Opportunity Score
- Price Book
- Probability
- Tracking Number
Change Requests
All fields are supported, incuding:
- Account Owner
- Annual Revenue
- Billing Address
- Customer Priority
- Parent Account
- SIC Code
- Tradestyle
- Upsell
- Year Started
Sync any Salesforce entity
Exalate for Salesforce allows syncing all the available objects and their fields within the Script connection. This page only shows the most popular and widely used objects and their fields.
Jira
Jira Software (Cloud and Data Center),
Jira Service Management, and Jira Data Center
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
“
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 to see Exalate in action
Control Your Data Flow Direction (one-way or two-way)
Set up and configure connections between Jira and Salesforce in any way you prefer. Control the direction of your data flow and choose between a one-way or a two-way Jira to Salesforce integration.
Automated Real-time Integration
Streamline your business workflows with automated, real-time Jira integration with Salesforce. Reduce manual work and exert control over data flow using custom automated triggers written in the platform’s native query language.
Bulk Operations
Sync current and historical data with bulk operations. Connect multiple existing entities using Bulk Connect. Start syncing entities automatically with the same trigger specifications using Bulk Exalate.
Advanced Integration Capabilities
Implement various sync possibilities using the AI-powered Groovy-based scripting engine. Use the embedded AI Assist chat window to generate scripts for controlling the sync on your end without affecting the destination.
Robust Integration
Refresh transactional sync queues to ensure your Salesforce Jira integration continues seamlessly from where it left off during downtime. Use the integrated retry mechanism to maintain uninterrupted and future-ready integrations.
Embedded Interface
Test your connection, view sync status, or connect existing entities with an integrated Exalate UI in Jira and Salesforce. Always stay up-to-date about progress reports within the platform you use.
Decentralized Integration
Retain independent control of your Jira integration to Salesforce, even in cross-company and multi-platform integration scenarios. Adjustments made on one side won’t 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 AI-enabled 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 |
Start for free
In practice:
...Or simply write a few lines of code
entity.entityType == “Custom Object Name”
replica.customFields.”CF Name” = issue.customFields.”CF Name”
In practice:
...Or simply write a few lines of code
import java.text.SimpleDateFormat;
import java.text.DateFormat;
def dateCustomFieldValue(replicaCustomField) {
def datePattern = “yyyy-MM-dd HH:mm:ss.S”; // define the desired date/time format
String dateString = replicaCustomField.value;
if (dateString) {
dateString = dateString.replaceAll(“\””,“”).trim();
DateFormat formatter = new SimpleDateFormat(datePattern);
date = formatter.parse(dateString);
return date.time;
}
}
entity.date__c = (Long) dateCustomFieldValue(replica.customFields.“DateCf”)
entity.datetime__c = (Long) dateCustomFieldValue(replica.customFields.“Date
In practice:
...Or simply write a few lines of code
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|”””
}
In practice:
...Or simply write a few lines of code
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
}
In practice:
In practice:
In practice:
...Or simply write a few lines of code
//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 |
01
install
02
connect
03
customize
04
synchronize
“
The team was very hands-on and very responsive. If we encountered an issue, they were able to resolve it quite fast.
Maarten Cautreels |
You can sync different work types like sprints, epics, bugs, etc., in Jira. On Salesforce, you can sync standard and custom objects. Some popular Salesforce objects are cases, opportunities, products, accounts, contacts, etc. You can also map, transform, filter, and sync any entity fields like summaries, descriptions, comments, attachments, etc. You can even sync third-party plugin fields like Elements Connect or Insight.
Exalate protects the data flowing through your Salesforce integration with Jira using security features such as JWT access tokens, role-based access controls, HTTP (HTTPs), TLS 1.2 and 1.3, and multi-factor authentication. You can find out more from the Trust Center or security whitepaper.
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 and Salesforce on their respective marketplaces.
Yes, docker installations for both Jira and Salesforce are available with Exalate. You can also deploy Exalate for Jira on-premise. 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 work items 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 and Salesforce 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.
