Jira-Salesforce Integration: Methods, What to Sync, and How To Set It up in 2026
Jira and Salesforce are two examples of best-in-class tools in their respective categories. But they rarely play well with each other, keeping technical teams and salespeople from collaborating effectively. Without an effective way to close the gap between these tools, teams can struggle and workflows can falter.
In this guide, you’ll learn about integrating Jira and Salesforce, including what options are available, what you can sync, and common use cases.
Overview: Jira-Salesforce integration
| Mulesoft Composer’s Jira Connector | One-way automation (e.g., Zapier) | Two-way sync (e.g., Unito) | |
| Sync direction | One-way, trigger-based automation | One-way, trigger-based automation. | Two-way. |
| Real-time or batch | Polling-based, not true real-time. | Real-time. | Real-time. |
| Field mapping depth | Supports both standard and custom Jira fields, with some gaps. Not all custom fields are supported. | Standard fields; custom fields and attachments usually not supported. | Standard fields, custom fields, comments, attachments, hierarchy mapping. |
| Setup time/effort | High. Technical skillset required. | Low. No-code with limited configuration. | Low. No-code setup. |
| Best for | Salesforce-native teams managing handoffs and escalations. | Simple visibility and handoffs. | Seamless collaboration across teams. |
What you can actually sync between Jira and Salesforce
Not every integration between Jira and Salesforce is the same, and one of the main differences between them is integration depth (i.e., how much they can sync.)
Work item previews
Some integrations create a read-only link between tools. A Jira work item, for example, might turn into a small panel in a Salesforce work item, listing a few fields like due dates, assignees, and status. You can’t interact with the Jira work item or update that work item by working in Jira. This kind of integration is good for keeping visibility on work happening in Jira, but you can’t collaborate across tools without manually moving data over.
Standard fields
Most integrations go beyond the preview level, supporting most, if not all, standard fields. “Standard” describes any field that’s already built into the tool, like due dates, assignees, and descriptions. Integrations can map similar fields between Jira and Salesforce automatically while others, like statuses and priority, need some transformation. Jira, for example, has rigid statuses that are more standard across projects than other project management tools. Salesforce deal stages, on the other hand, are more customizable.
Custom fields
Both Jira and Salesforce have custom fields, allowing you to fully customize your workspace to your workflows. Jira’s custom fields cover single-select, multi-select, text, number, date picker, user picker, and more. Salesforce custom fields include address, checkbox, currency, date, email, lookup relationship, and picklist.
Not all integrations can manage custom fields, since they usually require more transformation than standard fields. Some platforms might handle a few fields, while others handle most of them.
Comments and notes
Comments are often as essential to your workflows as the tasks and work items your integrations sync. A customer support agent’s escalated ticket might have several comments describing context from customers or troubleshooting steps that didn’t work. A developer’s Jira ticket might include questions for salespeople about custom development promised to potential clients.
Integrations that can sync comments back and forth help teams maintain context as they work across tools.
Attachments
Attachments allow teams to share deliverables, briefs, and context. Not all integrations can sync attachments, and those that do don’t necessarily all sync integrations in the same way.
Unito, for example, can support attachments in one of three ways: linked, copied, and streamed attachments.
Linked attachments create a hyperlink in synced work items. When you click on the link, it opens the original attachment in the tool it came from.
Copied attachments make the same attachment visible in multiple tools.
Streamed attachments create a unique page for each attachment, independent of either tool.
Hierarchies
Both Jira and Salesforce hierarchies, relationships between levels of work items. In Jira, for instance, the default hierarchy is Epic→Work Item (e.g., Story, Task)→Sub-task. But you can also customize this to something like Theme→Feature→Epic→Story→Bug→Sub-task for an agile product development workflow.
Integration platforms that don’t support hierarchies treat all work items like they’re the same, making it difficult to keep track of your work.
The 3 most common methods for setting up a Jira-Salesforce integration
Mulesoft Composer’s Jira Connector
Mulesoft Composer connects Jira to Salesforce through a no-code flow builder built on trigger-action logic. A trigger can be something like “a new issue is created in Jira” while an action might be creating a case or updating a record in Salesforce. Triggers work by polling the Jira API, checking for changes as often as every 15 seconds. Data moves in a single direction, meaning you need to build separate flows if you want data to move back and forth between Jira and Salesforce.
Mulesoft Composer is best-suited to routing Jira activity into Salesforce, like escalating support cases, creating or updating Salesforce records to match work items in Jira, and attaching files between systems.
There are tradeoffs with this method, however. A handful of standard and custom field types aren’t supported. And because each flow is one-way, there’s no single setting that keeps both systems continuously in sync. That means, if you need to move data back and forth between Salesforce and Jira, you need to set up at least two separate flows. That creates extra troubleshooting and maintenance costs.
Best for: Teams already running on Salesforce who need to trigger specific actions between Jira and Salesforce, rather than teams that need continuous, bidirectional syncing between these tools.
One-way automation (e.g., Zapier)
Third-part automation tools like Zapier use trigger-action logic to automate actions across Salesforce, Jira, and hundreds of other tools. These actions include automatically creating work items in Jira to match Salesforce items or updating a specific field in Salesforce when a similar field is changed manually in Jira.
These automation platforms excel at managing linear workflows, like approvals and escalations. They cover hundreds, if not thousands of tools, and usually a large number of fields, too. But each automation you build with these tools typically only covers a single action. Either it creates a work item or updates a single field. That means you can rarely cover every step in a workflow without creating (and managing) multiple automations.
Best for: Automating high-volume work item creation between Salesforce and Jira with minimal need for visibility or collaboration.
Two-way sync (e.g., Unito)
A two-way sync platform like Unito creates relationships between Jira work items and Salesforce items, keeping everything up to date as you work. Items are automatically created to match the ones you create manually, and fields are continuously updated in both tools.
Two-way sync platforms typically offer deep integrations that cover most, if not all, standard and custom fields, attachments, comments, and more. Some platforms can even sync hierarchies between tools. These deep integrations can handle all kinds of workflows, from simple approvals to handoffs and true cross-functional collaboration.
Best for: Working seamlessly across Jira and Salesforce with full visibility and no doubling up on tool licenses.
Use cases for a Jira-Salesforce integration
Ticket escalation
If you offer a software product or technical service, you’ll get support tickets that your frontline agents can’t resolve. These tickets get escalated to software developers, IT professionals, or other technical roles. The gap between the platform where tickets are first received (Salesforce) and the platform where the work to resolve them is planned (Jira) can be difficult to cross. Integrations close that gap, automatically syncing questions, comments, and ticket status.
Post-sales delivery
Sales teams that sell software or other technical products often need to promise custom development or new features to close large deals. When the deal closes, the sales team has to hand off the new client’s requirements to a software development team—who usually work in a tool like Jira. A Jira-Salesforce integration automates that handoff as soon as the deal closes, including all the context built up over your entire sales cycle. And if developers have questions, they can ask them in Jira and get answers when they’re added to Salesforce.
AI context
Both Jira and Salesforce have built-in AI agents that allow project managers, salespeople, and software developers to outsource repetitive tasks. But these AI agents have one big flaw: they typically only have access to the context in one tool. Jira’s agents access Jira projects while Salesforce agents access your Salesforce items. An integration can pull relevant context from both tools for both agents, ensuring tasks are executed more accurately and you get better answers.
Setting up a two-way sync with Unito
- Connect tool accounts to Unito: After signing up for Unito, click +Create Flow and connect Jira and Salesforce.
- Choose flow direction: Flow direction tells your Unito flow where you need new work items created. Most Unito flows are two-way, meaning they automatically create work items in both connected tools.
- Set rules: Unito rules use trigger-action logic to filter out work items you don’t want synced or automate certain actions. To build a rule, choose a trigger Unito should look for and the action it needs to take.
- Map fields: In most flows, Unito can automatically map fields in Jira with fields in Salesforce. From there, you can customize field mappings to match statuses across tools, send data from some fields to fields specific to your workflow, and more.
- Launch your flow: Once you map your fields, your flow is ready to launch. After an initial sync, Unito will check for changes in real-time.
Want to see what Unito can do?
Meet with a Unito product expert and see the impact Unito can have on your workflows.
FAQ: Jira-Salesforce integration
What Salesforce objects can I sync with Jira?
Unito can sync Jira issues with Salesforce opportunities, tasks, contacts, leads, and cases. Each Unito flow syncs one type of object for each tool.
How long does it take to implement a Jira-Salesforce integration?
The time it takes to integrate Jira and Salesforce depends on the integration platform you use. Pre-built connectors like Salesforce Connector for Jira can be deployed in a few weeks, though more complex iPaaS (integration platform as a service) platforms can take months. Unito’s two-way sync can be deployed within a few hours, whether you have technical knowledge or not.
Why should I integrate Jira with Salesforce?
Integrating Jira with Salesforce allows salespeople and development teams to collaborate more effectively. Whether it’s for planning Jira sprints with context from Salesforce or giving salespeople more visibility on product launches, integrations eliminate manual copying-and-pasting and constant status update meetings.
What workflows does Unito’s Salesforce-Jira integration support?
Unito’s Salesforce-Jira integration can support a number of workflows, including:
- Ticket escalation
- Software development
- Project management
- AI agent integration
- Time tracking and billing
- Record syncing
Which Jira versions does Unito support?
Unito supports Jira Cloud, Jira Server, and Jira Service Management.
Can I sync custom fields between Jira and Salesforce?
Yes, Unito supports syncing custom fields in both Jira and Salesforce. You can map them with other custom fields or standard fields.
Is Unito’s Jira-Salesforce integration bidirectional?
Yes, Unito’s Jira-Salesforce integration is a bidirectional sync by default, turning Salesforce items into Jira work items and vice-versa. Data from both tools also moves back and forth, meaning everyone has access to the same context, no matter where they’re working from.
How does Unito handle Salesforce API limits?
Salesforce limits API access to some plans, meaning that Unito integrations will only work if you use one of these Salesforce plans. Unito flows don’t usually hit Salesforce’s rate limits.
Do I need admin access to set up the integration?
You’ll find a full list of permissions you need to sync Salesforce in this Unito documentation. You don’t necessarily need admin access, but you will need API access, edit rights on any field included in your flow, access to custom fields included in flow, view all data permissions.
To sync Jira data with Unito, you’ll need both project-based and issue-based permissions. You’ll find a full list of these permissions here.
What happens to synced data if I disconnect the integration?
Unito doesn’t delete any of your data, so even if you disconnect an integration, you won’t lose any of the work items it’s created. Unito just won’t sync any new information.