start from JIRA
start from salesforce
BOOK A DEMO
flexible two-way sync
Powered by AI

Real-time Jira Salesforce Integration

Stop wasting hours on manual updates. Automatically sync cases, accounts, work itens and more between Salesforce and Jira.

Let Sales, Support, and Engineering stay perfectly aligned.

Book a demo
Start for Free

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...

        3.5/4 highest rated on the Atlassian Marketplace
        5/5 highest rated on Salesforce AppExchange
2000px-Dell_Logo.svg-e1507283755907

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-mark-square@2x

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
Book a demo
Start for Free

Simple or Advanced, We Got you Covered

Work with simple integration templates. Or, completely customize your sync. 

Sync Any Data

Set up one-way or two-way syncs between new or existing Jira and Salesforce entities. Sync issues, epics, sprints, etc in Jira. Sync any Salesforce entity such as cases, accounts, opportunities, contacts, custom objects, etc. Map fields by configuring the sync rules. Start automatic sync with triggers. 

Control your Jira Salesforce sync at a granular level.

Sync Custom Objects and Fields

Sync standard and custom Salesforce objects with custom Jira fields. Update the connected Salesforce Account details from the corresponding custom field in Jira.

In practice:

entity.entityType == “Custom Object Name”

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

Sync Date or Date/Time Fields

Sync custom fields in Salesforce like Date or Date/Time by converting them into a common format for Jira. 

In practice:

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

Sync Multiple Related Salesforce Objects to Jira

Present a Salesforce case object containing a contact and a linked account on the Jira side.

In practice:

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|”””
}

Elevate Comment Sync Capabilities

Sync comment threads and user mentions between Jira and Salesforce. Also, personalize the comment sync based on use case.  

In practice:

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 Incoming Cases as Different Work Types

Cases coming in from Salesforce need to be forwarded to three different work types based on status, urgency, assignee, etc. So the incoming case will appear as a support ticket, bug, or feature request.

In practice:
No need to code, simply add a trigger.

Sync Jira Insights to Salesforce Opportunities

Insights in Jira will prompt our Jira to Salesforce integration REST API to sync work items/tickets to Salesforce opportunities.

If you add an insight to a Jira ticket, it will automatically populate a field in the Salesforce opportunity with the number and status of that Jira ticket.

In practice:

Sync Picklist and Picklist Multi-select Fields

Select an item from a picklist field in the Salesforce case and sync it to a Jira work item’s custom field.

In practice:

//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

script mode

Your Integration, Your Rules

Full Control, Boosted by AI Assist

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
  • Deepen, change, adjust sync rules easily
  • Control outgoing and incoming data on each side
  • Simply mirror or customize mappings
Book a demo
Start for Free

“

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

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
GDPR-badge.png

How it Works

Install the Exalate app separately on all tools you wish to sync.

Connect multiple projects, instances, and platforms. 

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.

Set triggers to automate your sync based on specific conditions.

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

“

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 |

Start for Free

Exalate offers a 30-day Free Trial
Install it on both Jira and Salesforce to begin:

Sync fields from Work Items and Sprints

try it on jira

Sync fields from all Objects

try it on salesforce
request pricing

See it in Action

Let us show you how Exalate can fit your unique business needs.
book a demo
+2,500 clients worldwide

Stay Ahead in the Game With Your Jira Salesforce Integration

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 sync.

Streamline your business workflows with automated, real-time Jira Salesforce sync. Reduce the need for manual work. Enhance control over data flow using custom triggers in the platform’s native query language.

 

Sync historical data with bulk operations in Exalate. Connect multiple existing entities using Bulk Connect. Start syncing entities automatically with the same trigger specifications using Bulk Exalate.

 

Let your developers implement various sync possibilities using the Groovy-based scripting engine. Create scripts that manage synchronization on your end without affecting the destination.

Test your connection, view sync status or connect existing entities with an integrated Exalate UI in Jira and Salesforce. Always stay up-to-date within the platform you use.

FAQ

Answers to the most frequently asked questions

You can sync issues, sprints, and epics 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 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 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.