Jira Salesforce
integration.
Link Salesforce cases to Jira issues, so support sees engineering progress and engineering sees the customer behind the bug.
Jira Salesforce integration links Salesforce cases, accounts or opportunities with Jira issues, so support sees engineering progress and engineering sees customer impact. The Salesforce connectors on the Atlassian Marketplace are built by third-party vendors. Atlassian's own integration sends Service Cloud cases to Jira Service Management as alerts. MuleSoft also offers Jira connectors.
How it works
Does Atlassian offer its own Salesforce integration?
For Jira Service Management, yes. Atlassian documents a Salesforce Service Cloud integration in which new cases create alerts, a case set to Working acknowledges the alert and a closed case closes it. Two-way updates need a Premium or Enterprise plan. For Jira issue sync, the Marketplace apps come from third-party vendors.
The connector
Close the loop. Support to engineering.
Techila Global Services is a Salesforce Summit Partner. We connect Salesforce and Jira so an escalated case becomes a linked Jira issue, and status and comments come back to the case without copy and paste.
We help you pick a Marketplace app, a MuleSoft flow or a custom build, then set up the Salesforce side: case fields, permissions and the agent's view of the linked issue.
Jira Salesforce connectors compared: what are the ways to connect them?
| Option | What it moves | Limits from the official page |
|---|---|---|
| Third-party apps on the Atlassian Marketplace | Varies by app: typically Jira issues linked to Salesforce cases, accounts or opportunities | Built by third-party vendors, not Atlassian. Check each listing for hosting (Cloud or Data Center), direction and price. |
| Atlassian's Jira Service Management integration with Service Cloud | Service Cloud cases into Jira Service Management as alerts; case status acknowledges or closes the alert | Two-way updates need Premium or Enterprise. Set up by adding an Apex class, an Apex trigger and a remote site setting in Salesforce. |
| MuleSoft Composer Jira connector | No-code flows: create, update and get issues, add comments and handle attachments, triggered by new or updated issues | Needs the Administrator Jira global permission. |
| MuleSoft Anypoint Jira connector | Any flow a Mule application defines, using the Jira REST API v3 | Jira Cloud only. Basic or OAuth2 authentication; personal access tokens are not supported. |
| Custom build on both APIs | Whatever you design | You own the code, monitoring and API changes. |
We help you choose the option, then build, test and support it as part of our Salesforce integration services. See Salesforce integrations, or talk to us about your setup.
What should a case-to-issue flow do?
- An agent escalates a case, or a rule does, and a Jira issue is created with the case number and customer details engineering needs.
- The Jira issue key is stored on the case, so both teams can find the other record.
- Status changes and selected comments in Jira update the case.
- When the fix ships, the case is flagged for the agent to confirm with the customer and close.
What moves between a case and a Jira issue?
- Escalated case creates an issue (from Salesforce to Jira)
- Issue key stored on the case (from Jira to Salesforce)
- Status changes and selected comments (from Jira to Salesforce)
Decide early which comments cross between systems: customer details may not belong in Jira, and internal engineering notes may not belong on a case. To design yours, book a call.
How do you set up a Jira Salesforce integration?
The tool changes, but the order of work stays the same:
- Agree the escalation rule: which cases become Jira issues, in which Jira project and issue type.
- Pick the option from the table above, checking hosting (Jira Cloud or Data Center), direction and price on each listing.
- Create integration users on both sides with only the permissions they need. MuleSoft Composer's Jira connector, for example, needs the Administrator Jira global permission.
- Add the cross-reference fields: the Jira issue key on the case, and the case number on the issue.
- Map fields and statuses, including which Jira statuses move the case and who closes it.
- Decide what crosses: comments, attachments and customer details, and what stays private on each side.
- Test in a sandbox with real case volumes, then roll out to one support team before the rest.
Common Jira Salesforce integration pitfalls
- Every case becomes an issue. Engineering's backlog fills with questions that support could answer. Escalate confirmed bugs and feature requests only.
- Status loops. If both systems can change status and both sync it, updates bounce back and forth. Give each status change one owner.
- Customer data in Jira. Names, emails and attachments copied into Jira may reach people who should not see them. Sync only what engineering needs.
- Hosting mismatch. MuleSoft's Anypoint Jira connector is for Jira Cloud only, and Marketplace apps differ by hosting. Check Cloud or Data Center before you buy.
- Personal accounts as integration users. When that person leaves, the sync stops. Use dedicated integration users on both sides.
- No one watches the errors. A failed sync is invisible until a customer asks. Name an owner for the error log.
What does a Jira Salesforce integration cost?
Connector licences are usually the smallest part. Atlassian Marketplace apps for Jira Cloud are priced on the number of users in your Jira instance, not the number of support agents, and every Cloud app has a 30-day free trial. Two examples from the Marketplace pricing pages, read on 11 November 2026, monthly billing:
| Option | List price shown | Notes |
|---|---|---|
| Connector for Salesforce & Jira (Appfire) | Free up to 10 users; USD 321 a month for 100 users | Jira Cloud; price rises with the Jira user tier |
| Salesforce Connector for Jira (Getint) | USD 320 a month for 100 users | Jira Cloud; price rises with the Jira user tier |
| Atlassian's Jira Service Management integration with Service Cloud | Part of your Jira Service Management plan | Two-way updates need a Premium or Enterprise plan |
| MuleSoft | Packages start at USD 2,000 a month, billed annually | Credit-based; MuleSoft quotes each package through sales |
The rest of the cost depends on the work, not the licence: how many projects and case types escalate, how many fields and statuses map, whether attachments and comments sync both ways, Jira Cloud or Data Center, and who monitors the integration after launch. A Marketplace app with standard mappings is the cheapest route; MuleSoft makes sense when Jira is one of several systems feeding Service Cloud. If IT runs ServiceNow alongside Jira, see our ServiceNow Salesforce integration guide.
Architecture
How does data move between Salesforce and Jira?
Salesforce
App, middleware or API
Jira
What's included
What does a Jira Salesforce integration project cover?
Looking for delivered work? See case studies
FAQ
Frequently asked questions.
What architects ask before commissioning a Techila integration.
The Salesforce connectors listed on the Atlassian Marketplace come from third-party vendors. Atlassian's own documentation covers a Service Cloud integration for Jira Service Management that turns cases into alerts.
Atlassian says a new case creates an alert, a case set to Working acknowledges it and a closed case closes it. Updates back to Salesforce need a Premium or Enterprise plan, and setup adds an Apex class and trigger in Salesforce.
Yes. MuleSoft Composer has a no-code Jira connector for creating and updating issues and adding comments. The Anypoint Jira connector uses the Jira REST API v3 and works with Jira Cloud only.
It depends on the option. MuleSoft's Anypoint Jira connector is for Jira Cloud only. Some Marketplace apps list Data Center versions; check the hosting options on each listing.
Marketplace connector prices depend on your Jira user tier. On 11 November 2026, Appfire's Connector for Salesforce & Jira listed free up to 10 users and USD 321 a month for 100 users, and Getint's Salesforce Connector for Jira listed USD 320 a month for 100 users. Setup, mapping and support depend on scope.
Usually not. Most teams create issues only for confirmed bugs or feature requests, so engineering's backlog stays clean and support keeps ownership of the customer conversation.
Sources
Last reviewed:
- Atlassian Support, Integrate with Salesforce Service Cloud (Jira Service Management Cloud) (read 10 November 2026)
- Atlassian Marketplace, Search results for Salesforce (read 10 November 2026)
- Atlassian Marketplace, Connector for Salesforce & Jira (Appfire): Cloud pricing (read 11 November 2026)
- Atlassian Marketplace, Salesforce Connector for Jira (Getint): Cloud pricing (read 11 November 2026)
- MuleSoft, MuleSoft pricing (read 11 November 2026)
- MuleSoft, MuleSoft Composer: Jira connector reference (read 10 November 2026)
- MuleSoft, Jira Connector 1.2 (read 10 November 2026)
- Salesforce Architects, Integration patterns (read 10 November 2026)
Talk to an expert about Jira Salesforce integration
Tell us what you need. We reply within 1 business day.
Let's plan your next Salesforce program.
We reply within 1 business day · +1 617-777-9873
See case studies