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. |
Why integrate Jira and Salesforce
Integrating Jira and Salesforce typically means closing the gap between technical and customer-facing teams. That can be for ticket escalation, post-sales delivery, or collaborating on product-facing marketing campaigns. The handoff between these tools typically involves a single person copying and pasting data back and forth, leading to misalignment, extra data entry work, and lost updates. No matter what use case this integration serves, it creates the following benefits:
- Fewer licenses: Teams that frequently collaborate across Jira and Salesforce often need licenses in both tools. The right integration can eliminate these doubled licenses, saving you on tool budget you can reallocate elsewhere.
- Seamless collaboration: Handoffs between Jira and Salesforce add friction to your workflows that can manifest in lost time, late updates, and missed deadlines. With the right integration, those handoffs are handled automatically.
- Smoother workflows: Handoffs aren’t the only time collaboration across Jira and Salesforce can be challenging. Getting updates from each tool, checking on customer data, and validating product information all become easier with an integration.
- Better reporting and visibility: The work happening in Jira and Salesforce often contribute to larger workflows, but reporting on that work
- Real-time updates: Working across tools like Jira and Salesforce inevitably brings delays, often due to waiting for information to travel the gulf between tools. The right integration updates work items in Jira and Salesforce automatically to match the work happening in either tool. No waiting around for updates.
Integration depth 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 have 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 4 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-party 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.
Custom API development
Both Jira and Salesforce have extensive API documentation that allows software developers and engineers to build custom integrations between them. An in-house build can be the best option for specific workflows that other integration options can’t support, strict data residency requirements, or even organizations that have a dedicated integration team. Because you can customize the integration to your specifications, it can suit your needs better than other options.
That said, this approach does have its disadvantages. First is the build. You’ll be pouring both time and budget into building your custom integration which means that, even with a dedicated integration team, you’ll be pulling resources away from other opportunities. Second is maintenance. When you use an integration from a third-party vendor, maintenance is rarely your responsibility. With a custom-built integration, all that maintenance is your responsibility. That takes up resources, as well.
Best for: Organizations that have integration needs so specific that third-party vendors can’t meet them, or where a custom build has a better return on investment.
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.
How to choose a Jira-Salesforce integration
When choosing between options for a Jira-Salesforce integration, consider the following criteria.
One-way or two-way
For most workflows, this should be the first criteria you consider. Simple handoffs might only require a one-way integration, while true seamless collaboration usually needs a two-way sync. If your workflows go beyond the need for sequential automation, then a two-way sync is the best option.
Custom field and custom object support
Not every integration platform can handle custom fields or objects. If your workflows rely on tools with extensive customization, you need an integration that can support that. Otherwise you’ll be constantly relying on workarounds that eat up more time and energy than the integrations save.
Real-time or scheduled updates
Real-time updates mean your teams always have the most up-to-date information when they work, but not all workflows require this. Most integration platforms push changes in batches, and that may be enough for simple handoffs.
API limits
An API (Application Programming Interface) surfaces information in a tool so integrations can sync it to other tools. But some tools have API limits, meaning only a certain amount of data can be pulled over a specific period. If your use case involves a massive amount of data, it’s worth seeing if these limits exist and how different integration tools circumvent them.
Who can set it up
Some integration platforms are more complex, meaning you need a team with technical skills to set them up. Others can be deployed by the average business user. One approach isn’t necessarily better than the other, it’s just a matter of which one fits your organization best. A larger company with the technical resources to spare can pick any type of deployment, but smaller teams might want an integration anyone can deploy.
Error handling
Not every integration platform handles errors the same way. Some stop trying to sync data the moment they run into an issue. Others keep trying to sync, potentially creating duplicate items with each failed attempt. When researching an integration platform, try to find documentation about how errors are handled so you know what to expect.
Security and data residency
Since an integration platform might have access to sensitive, proprietary data, security is essential. Researching a platform’s security certifications and frameworks gives you a sense of how secure your data will be. It can also ensure you use a platform that meets any specific security requirements you have, whether that’s due to the jurisdiction you operate in (e.g., CCPA) or your industry (e.g., HIPAA).
Pricing model
A platform’s pricing model should be as important of a consideration as that platform’s capabilities. Using the wrong pricing model can quickly lead to ballooning costs as you use an integration more and more. Consider whether a per-task, per-connector, per-user, or a per-item-in-sync model makes the most sense for your needs.
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.
Feature request handoff
Whether they come from customers, prospects, or even a public request forum, feature requests can improve your product or service tremendously. But the people who notice the requests are rarely the same as the ones working on them. Integrating Jira and Salesforce allows feature requests to be handed off without any context going missing in the transfer. With the right platform, you can even have feature requests created in Jira automatically when a deal in Salesforce gets blocked.
Status feedback to an account team
A two-way sync integration can sync data back from Jira after a case is escalated from Salesforce. This allows CS and other customer-facing teams to keep track of development work in Jira without needing to jump back and forth between tools or keeping up with long email chains.
Priority and SLA routing
An integration can pair Salesforce cases with Jira issues, maintaining priority across tools. That means teams in both Jira and Salesforce can track progress using the same SLA clock, preventing misunderstandings.
Release coordination
Software product releases typically involve marketing support, communication with customers, and more. An integration can automatically share release notes and other details from Jira to Salesforce, giving customer-facing teams everything they need to plan their campaigns.
Multiple Jira projects and one Salesforce organization
In larger organizations, multiple engineering teams might work on multiple software projects that salespeople and other customer-facing teams need to be aware of. An integration can pair the multiple Jira projects representing that work with a single Salesforce organization, keeping everyone up to date.
Jira-Salesforce integration best practices
No matter which integration you pick, consider the following best practices.
- Start with a small pilot project between a few work items in Jira and Salesforce. This allows you to test integrations and adjust them before you deploy them more broadly.
- Evaluate the results of a pilot project before implementing integrations at scale. Look for places where integrations save your teams time as well as situations where they might not be as effective as you expected.
- Consider whether your chosen integration platform is accessible enough for business users or whether you need to restrict it further to technical teams.
- Regularly review the integrations you use, at least yearly. Compare capability, price, and connector availability with other vendors.
- Use built-in integrations where possible, at least initially, and enhance them with third-party integrations as your needs start to evolve.
What breaks and how to fix it
Comment sync loops
This usually isn’t a sync loop — it’s attribution. By default, Unito posts synced comments and updates under the account of whoever set up the flow, so every comment can end up looking like it came from one person, even when five different reps and developers wrote them. The fix is a dedicated service or bot account for the flow, so synced activity carries a distinct identity instead of one teammate’s name showing up everywhere. If you’re seeing genuine duplicate comments (not just misattributed ones), check for more than one flow watching the same Jira project and Salesforce object — that’s the actual cause when it happens.
Assignees or owners aren’t syncing
This is almost always a mapping or permissions issue, not a compatibility one. Check that Assignee and Owner are explicitly paired in your field mappings. On the Jira side, only users who are assignable on the project show up as valid sync targets — a Salesforce case owner with no matching, assignable Jira account simply won’t sync until that’s fixed.
Jira’s workflow and Salesforce’s Case status don’t line up
A Jira workflow (To Do → In Progress → Code Review → Done) rarely maps cleanly onto a Salesforce Case’s Status field (New → Working → Closed). Unito handles this with status mapping: pair values individually for a strict 1:1 relationship, or group several source statuses into one target value. Grouping has a quirk worth knowing before you configure it — Unito always syncs the first status in a grouped set, so an issue moving between two grouped statuses can look stuck on the Salesforce side. If every status change needs to reflect accurately, map values individually instead of in groups.
Picklist fields reject synced values
Salesforce picklists only accept predefined values, while a lot of Jira fields are free text or use differently worded options. Unito auto-matches similar option names, but anything that doesn’t line up needs a manual value pairing — and a Salesforce picklist will silently reject any incoming value it doesn’t recognize as valid. Before launching a flow, walk through every possible Jira value for a mapped field and confirm each one has a matching Salesforce option.
Attachments don’t come through
Salesforce and Jira cap attachment sizes differently, and the smaller limit always wins. Salesforce’s standard Attachment object tops out at 25MB per file (Salesforce Files, a separate object, allows up to 2GB). Jira Cloud defaults to 1GB per file, and Jira Data Center defaults to a much smaller 10MB. A large file attached in Jira Cloud can fail to sync over if it clears Salesforce’s 25MB ceiling — worth flagging for teams that attach screen recordings or design files to tickets.
Deleting a record on one side doesn’t delete it on the other
This is usually by design, not a bug. Integrations rarely delete an item, comment, or field value on one side just because it was deleted on the other, and won’t recreate a deleted item on a future sync — the assumption is that a deletion was intentional. To fully remove a record from both systems, delete it manually on both ends. Re-launching a flow after this won’t restore anything; it will only re-link items that still exist on both sides.
A large first sync stalls partway through
This shows up when integrations are pulling and writing thousands of records during an initial sync and runs into Salesforce’s API ceiling. If a flow does hit this, integrations will pause and surface a rate-limit error rather than fail silently. Narrowing the initial sync with rules — so you’re not backfilling years of closed cases on day one — is the most common fix, alongside increasing Salesforce’s API allocation if the org’s plan supports it.
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.
What you can sync between Jira and Salesforce
| Jira field | Salesforce equivalent | Sync direction |
| Affected Version | Custom | Two-way |
| Assignee | Case Owner | Two-way |
| Attachment | Attachments | One-way |
| Comment | Internal Comments | Two-way |
| Component | Product | Two-way |
| Date Picker (custom field) | Date (custom field) | Two-way |
| Date/Time (custom field) | Date (custom field) | Two-way |
| Description | Description | Two-way |
| Due Date | Date (custom field) | Two-way |
| Epic | Parent Case | Two-way |
| Fix Version | Number (custom field) | Two-way |
| Float (custom field) | Number (custom field) | Two-way |
| Issue ID | Number (custom field) | One-way |
| Issue Number | Number (custom field) | One-way |
| Issue Status | Status | Two-way |
| Issue Type | Type | Two-way |
| Label | Picklist (custom field) | Two-way |
| Link to Issue | URL (custom field) | One-way |
| Multi-Checkbox (custom field) | Picklist (Multi-select) (custom field) | Two-way |
| Multi-Select (custom field) | Picklist (Multi-select) (custom field) | Two-way |
| Multi-User (custom field) | Picklist (Multi-select) (custom field) | Two-way |
| Original Time Estimate | Number (custom field) | One-way |
| Priority | Priority | Two-way |
| Project Name | Text (custom field) | One-way |
| Radio Button (custom field) | Picklist (custom field) | Two-way |
| Remaining Estimate | Number (custom field) | One-way |
| Reporter | Created By | Two-way |
| Resolution | Text (custom field) | Two-way |
| Security Level | Text (custom field) | Two-way |
| Single-Select (custom field) | Picklist (custom field) | Two-way |
| Sprint | Text (custom field) | Two-way |
| Sprint End Date | Date (custom field) | One-way |
| Sprint Start Date | Date (custom field) | One-way |
| Story Point Estimate | Number (custom field) | Two-way |
| Subtask | No equivalent | N/A |
| Summary | Description | Two-way |
| Text Field (custom field) | Text (custom field) | Two-way |
| Textarea (custom field) | Text (custom field) | Two-way |
| Time Spent | Number (custom field) | Two-way |
| URL (custom field) | URL (custom field) | Two-way |
| User Picker (custom field) | Picklist (custom field) | Two-way |
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.
What’s the difference between Salesforce Connect and a Jira–Salesforce integration?
Salesforce Connect is a native Salesforce feature, not an integration platform. It lets Salesforce display external data (via OData or the Salesforce adapter) as read-only external objects inside your org, without duplicating records. It doesn’t talk to Jira, doesn’t create work items, and doesn’t sync updates back and forth. A Jira–Salesforce integration requires a separate tool — a pre-built connector, automation platform, or two-way sync tool like Unito — built specifically to move data between the two systems.
Can I sync Salesforce Cases to Jira issues automatically?
Yes, this is one of the most common Jira–Salesforce use cases, and most integration approaches support it. Trigger-based tools (MuleSoft Composer, Zapier) can create a Jira issue whenever a Case meets specific criteria. Two-way sync platforms like Unito go further, keeping the Case and issue linked afterward so status, comments, and field updates continue flowing both ways rather than only at creation.
How do I map Salesforce Opportunities to Jira Epics?
Start by pairing the object types (Opportunity to Epic) in your platform’s flow builder, then map comparable fields — Opportunity Name to Epic Name, Amount and Close Date to custom fields, Stage to an Epic status or label. Since Opportunity stages and Jira Epic statuses rarely match 1:1, most platforms need manual value-pairing for that field specifically. Add rules to control which opportunities create epics in the first place, rather than syncing your entire pipeline.
Can I connect multiple Jira instances to one Salesforce org?
Generally, yes. Most platforms — including MuleSoft Composer, Zapier, and Unito — let you build a separate connection or flow for each Jira instance or project, all pointed at the same Salesforce org. There’s typically no hard limit on how many Jira sources can feed one org, though each flow is usually configured, ruled, and mapped independently, so the setup and maintenance effort scales with how many you add.
How are conflicts handled when both sides change at once?
This varies by platform and isn’t always documented in detail. The common approaches are last-write-wins (the most recent change overwrites the other), one-directional field ownership (a given field only ever updates in one direction, so there’s nothing to conflict), or manual review queues for ambiguous cases. Check a platform’s specific documentation before relying on it for fields that both teams edit frequently, since the wrong assumption here can cause silent data loss.
Can I sync historical data or only new items?
Both are usually possible, but check the default. Many platforms — Unito included — apply a default rule that only syncs items created after the flow launches, specifically to let you test safely before committing to a full backlog sync. Backfilling historical Cases, Opportunities, or issues typically means removing or adjusting that default rule, and large backfills are also where you’re most likely to hit API rate limits (see below).
Can I filter which comments sync?
Some platforms support this, but granularity varies widely. Rule-based filtering on comment visibility (public vs. internal) is fairly common, especially for Case-to-issue workflows where you don’t want internal engineering notes reaching a customer-facing Case. Filtering by comment author or keyword is less commonly supported. If comment privacy matters for your workflow, confirm the specific platform’s comment-filtering options before launch rather than assuming parity with its other field rules.
Which Salesforce objects can be synced?
This depends on integration depth. Most platforms that connect to Salesforce’s API can reach Opportunities, Cases, Contacts, Leads, Accounts, Tasks, and custom objects. Unito, for example, syncs Jira issues with Salesforce opportunities, tasks, contacts, leads, and cases, with each flow covering one object type per tool. Platforms with shallower Salesforce support may be limited to Cases or Leads only — worth confirming before assuming broad object coverage.
Does a Jira–Salesforce integration work with Jira Service Management?
Most integration platforms treat Jira Service Management as a variant of Jira Cloud and Data Center, so the same integration methods generally apply. That said, JSM-specific fields — request type, customer satisfaction ratings, SLA fields — aren’t always supported at the same depth as standard Jira Software fields, since they’re newer and less universally implemented across connectors. Confirm JSM-specific field support directly rather than assuming full parity with standard Jira issue fields.
How much does a Jira–Salesforce integration cost?
It depends heavily on pricing model, not just plan tier. Per-task tools like Zapier scale cost with automation volume; per-connection platforms like Exalate or Getint charge based on the number of linked project/object pairs; two-way sync platforms like Unito typically price by items in sync. Enterprise iPaaS options (MuleSoft, Workato) are usually quote-based and can run considerably higher, reflecting implementation complexity rather than just usage.