Jira Salesforce Integration — Two Ways
The Jira Salesforce connector that keeps both tools in sync automatically. Integrate once, and every case, issue, and update flows between them in real time.
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...
4.3/5
Highest Rated Integration App on the Atlassian Marketplace
Sync Exactly What Your Teams Need
Sync any entity using a one or two-way mapping. Configure and map the entities precisely as you require them.
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
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
“
Exalate is stable, flexible, customizable, and pretty easy to set up and use.
ALEXANDER SINNO
How it Works
Connect
Easily connect multiple projects, instances, and platforms. With local, or external partners.
Customize
Set your sync rules to make sure the right data is shared.
Prompt Exalate’s AI to generate rules, or fine-tune with Groovy-based custom mappings and logic for complete control.
Automate
Set triggers to automate your sync based on specific conditions.
Synchronize
Now your connected instances will exchange information automatically. Happy syncing!
Get the Most Out of Your Integration
Sync in Real-Time
Two-way, real-time sync between platforms. Updates flow automatically. No manual exports, no delays.
Connect Any Number of Instances
Connect multiple projects, instances, and platforms. Use different rules for each connection.
Know What Failed and Why
Get AI-powered recommendations for resolving the issue, including possible fixes and next steps.
AI Assisted SetUp
Describe your integration goal. Aida reviews your sync rules and connector type, then suggests script changes
Only Sync What Matches
Set various conditions for automatic synchronization.
Sync Visibility, Right Where You Work
Check the real-time status of your active syncs, spot failures, and trigger a manual push. All from a browser extension, without opening the Exalate console.
ai assisted script
Your Integration, Your Rules
Full Control, Boosted by Aida AI
Exalate comes with default sync rules, that can be adapted to your specific needs.
Build your unique integration rules with just a few lines of Groovy Script – or a few prompts.
- Deepen, change, adjust sync rules easily
- Control outgoing and incoming data on each side
- Simply mirror or customize mappings
- Track changes with version history
- Move confidently with draft mode
“
We can do almost anything we want with the sync thanks to its groovy script.
I can say I haven’t seen any other apps as flexible as Exalate.
Daniel Miks
Why Exalate is
Secure by Design
- Single-tenant architecture – no shared infrastructure
- Encryption in transit and at rest
- Automatic recovery from outages
- ISO 27001:2022 certified
- 24/7 threat monitoring with SentinelOne
Simple or Advanced, We Got you Covered
Work with simple integration templates. Or, completely customize your sync.
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:
No need to code, simply add a trigger.
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 |
Pricing Built for Scale, Not Surprises
Exalate offers a 30-day Free Trial
Starter
Small teams with straightforward synchronization needs
Scale
Growing teams with moderate synchronization volume
Pro
Organizations needing enterprise systems
pricing per integration starts atThis is the entry price for the lowest-cost integration. Your price depends on which systems you connect, items in sync, environments, SLA/support, and add-ons. To get a tailored quote, contact sales.
$
550
/mo
Billed annually
Enterprise
Large-scale deployments with custom requirements
Let's talk
Get in touch for your custom pricing
& more
See the New Exalate in Action
Let us show you how Exalate can fit your unique business needs.
trusted by clients worldwide
It’s a connection between Jira and Salesforce that keeps issues and cases synchronized automatically. When a case changes in Salesforce, the linked Jira issue updates. When a Jira issue changes, Salesforce reflects it too.
Install Exalate on both Jira and Salesforce, initiate a connection from one side, and accept it on the other. You then configure which fields, objects, and projects are in scope. A basic integration takes about 15 minutes.
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 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 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.
Cases, Opportunities, Accounts, Contacts, Change Requests, and any custom objects. All fields within each object are supported, including custom fields.