You connect Jira to Salesforce with an AppExchange or Atlassian Marketplace connector such as Appfire’s Connector for Salesforce & Jira, Exalate or Peeklogic, with a sync tool such as Unito or Zapier, or with a custom build on both APIs. The connector route suits most teams: support raises a Jira issue from a Salesforce case, engineering works it in Jira, and status and comments flow back to the case.
Ways to connect Jira and Salesforce
| Route | Best for | Direction | What it costs |
|---|---|---|---|
| Connector app (Appfire, Exalate, Peeklogic) | Support-to-engineering escalation from cases | Two-way: issues, status, comments, attachments | Per-user app subscription; low setup |
| Sync tool (Unito, Zapier) | Simple flows, a few fields, low volume | One or two way, per flow | Per-task or per-sync pricing |
| Custom API build | Unusual objects or rules no connector expresses | Whatever you build | Highest build cost; you maintain it |
What maps to what
| Jira | Salesforce | Notes |
|---|---|---|
| Issue (bug, task) | Case | The common pattern: an escalated case links to one or more issues |
| Issue or epic | Opportunity or Task | For feature requests that block a deal |
| Status | Case status or a custom field | Map each Jira status to one Salesforce value |
| Comments and attachments | Case comments and Files | Decide which comments are public to the customer |
| Project | Product or Account | Routes new issues to the right team |
Limits to plan for: connectors are licensed per user on one or both sides, so count who needs access; workflow transitions in Jira do not always map one-to-one onto case statuses; and every sync uses Salesforce API calls. Jira is one of the Salesforce integrations we build.
How to set up a Jira–Salesforce connector
- Decide the pattern first. Which cases get escalated to engineering, which Jira project receives them, and who in support owns the link once it exists.
- Install both halves. The connector has a Jira app from the Atlassian Marketplace and a Salesforce package from AppExchange. Authorise each with a dedicated integration user rather than a person’s login, so the connection survives someone leaving.
- Map objects, fields and statuses. Cases to issues, the fields each side can see, and every Jira status to exactly one Salesforce value. Decide here which comments flow back, and whether any of them can reach the customer.
- Put the action where agents work. Add the create-and-link action and the linked-issue panel to the case page layout, so escalating a case is one click and its Jira status is visible without leaving Salesforce.
- Test in a sandbox against a test project, then roll out to one support team before everyone.
What breaks in production
A new Jira status nobody mapped
Engineering adds a workflow status in Jira, the connector has no Salesforce value for it, and linked cases stop updating without an error anyone sees. Review the status mapping whenever a Jira workflow changes, and alert on sync failures rather than waiting for an agent to notice.
Internal comments reaching the customer
If synced Jira comments land as public case comments, an engineer’s note can end up in the customer’s portal or email thread. Sync them as private by default, and make publishing a deliberate step.
The integration user
Most connection failures come from the integration user on one side: an expired token or password, a permission removed in a clean-up, or an IP restriction on its profile. Give it its own profile, and put its credentials on someone’s calendar.
API limits and licence counts
Every sync consumes Salesforce API calls, and a busy Jira project can use more of the daily allowance than expected. Licence counts drift the same way, as more agents and engineers need the link. Check both before go-live, not after the first outage.
Jira–Salesforce FAQ
Can Jira integrate with Salesforce?
Yes. Connector apps such as Appfire’s Connector for Salesforce & Jira, Exalate and Peeklogic link Salesforce cases to Jira issues and sync status, comments and attachments both ways.
Can I create a Jira issue from a Salesforce case?
Yes, that is the most common use. A connector adds an action to the case that creates a linked Jira issue, and the issue’s status then shows on the case.
Do I need a paid connector to integrate Jira and Salesforce?
For a reliable two-way sync, usually yes. A sync tool such as Zapier covers a simple one-way flow, and a custom build avoids the licence but costs more to build and maintain.