Quick answers
- Does Atlassian have a native Salesforce integration?
- Not a current sync app: Jira Cloud for CRM (Official) "has been archived" (Marketplace). Atlassian's Service Cloud integration raises Jira Service Management alerts from new cases, and Rovo's connector supports search and chat. Neither syncs cases with Jira work items.
- What does Salesforce recommend?
- Its Jira integration page says "The recommended solution for Jira integrations is MuleSoft".
- What's the quickest route?
- For a common pattern, such as escalating a case to Jira and showing its status in Salesforce, usually a Marketplace app.
- Does Rovo sync Salesforce with Jira?
- No. It lets people search or chat across Salesforce data, but doesn't create or update work items.
Start with what each system owns
Write down what people need, then decide field by field which system owns each value and which way it flows. A common split: Salesforce owns the account, contact and case priority; Jira owns status, assignee and resolution. Agreeing this before implementation beats untangling conflicting records after go-live.
- Agents see whether engineering has picked up a case, without leaving Salesforce.
- Engineers get enough customer context, without a Salesforce licence.
- Product and sales see which accounts a bug affects.
Option 1: a Marketplace connector app
Examples listed on the Atlassian Marketplace include connectors from Appfire, Exalate, Getint and zAgile. Listings differ: some sync cases two ways, one is built on Forge, some also cover Data Center. Senzo doesn't endorse a particular vendor.
Option 2: MuleSoft or another integration platform
MuleSoft, which Salesforce owns, has two Jira connectors. The Anypoint Connector "is only for the Cloud version of Jira" (MuleSoft). MuleSoft Composer's connector needs a Jira administrator and polls for changes, at a documented 15-second interval set per flow; "a shorter frequency consumes more API calls" (MuleSoft).
It fits when you already run a platform or several systems share data. It adds a subscription and a third place where logic lives.
Option 3: build it on both platforms' APIs
Jira offers automation's Send web request and Incoming webhook; Salesforce offers Flow HTTP callouts, Platform Events and Outbound Messaging. Jira reads webhooks as JSON, so you usually need a listener in the middle. A custom build may avoid a connector subscription, but you own three things:
- Rate limits and retries: Jira Cloud returns HTTP 429 over a limit; back off exponentially, and retry only idempotent calls that carry a Retry-After header.
- Duplicate and out-of-order events: Salesforce outbound messages can arrive out of order or twice, and Jira webhooks more than once.
- Failure recovery and ownership: failures go where someone sees them, and someone owns the tokens, which expire within a year.
Option 4: Rovo, if people only need to find Salesforce data
Rovo's synced connector indexes Accounts, Opportunities, Contacts, Cases and Campaigns; its direct connector "does not index any data" and uses each user's own access. It shares your Salesforce API quota, and Rovo stops ingestion when available quota falls below 50%. It finds Salesforce data; it doesn't sync it with Jira. See our Rovo and Atlassian AI page.
The options side by side
| Route | Does | Best when | Watch for |
|---|---|---|---|
| Marketplace app | Syncs or links records with work items | A common pattern, no integration team | Vendor data handling; Forge or Connect |
| MuleSoft or iPaaS | Moves and transforms data across systems | You run a platform, or several systems | Subscription; a third place for logic |
| Custom build | Exactly the events and fields you design | No app fits, or logic is specific | Retries, duplicates, token expiry, ownership |
| Rovo connector | Search and chat across Salesforce data | People need to find data, not sync it | No Jira sync; shares your API quota |
Design decisions that matter more than the tool
- One case, many work items?Decide how cases and bugs link, and how status reaches each case.
- Statuses don't map one to oneMap Jira's statuses to the few states agents tell customers.
- Comment visibilityAn internal engineering note shouldn't end up in a customer email.
- Customer data in JiraSync only the fields engineers need; each extra one spreads personal data.
- Identity on each sideA dedicated, least-privilege integration identity, not a staff login.
- Site-specific IDsIDs can differ between sandbox and production; re-check before go-live.
Example: escalating a Salesforce case to Jira engineering
A typical design, not a specific customer deployment.
| Step | What happens | Decision |
|---|---|---|
| 1. Escalate | An agent escalates a case to engineering | Who can escalate, and which cases |
| 2. Create or link | Pick an existing work item, or create one | Many cases can share one work item |
| 3. Send context | Case reference, product, priority, summary | Contact details stay in Salesforce |
| 4. Engineering works | Engineers update the work item in Jira | Jira owns status and resolution |
| 5. Status returns | Each linked case gets a simpler status | Statuses agents tell customers |
| 6. Comments | Internal comments stay unless marked to cross | A visibility rule each way |
| 7. Repeats | A repeated event is recognised and ignored | No duplicate work items |
| 8. Failures | Failed updates are logged, retried or reconciled | Failed events aren't lost |
What a Salesforce Jira integration costs to own
Estimate each row over 12 and 36 months. The route that's cheapest to set up isn't always the cheapest to own.
| Cost | Marketplace app | iPaaS | Custom build |
|---|---|---|---|
| Licensing | App subscription, plus Salesforce-side licences | Platform subscription, possibly shared | No connector fee; hosting still costs |
| Implementation | Configuration, mapping, testing | Flow design, configuration, testing | Development, testing, security review |
| Support | Administration and vendor support | Platform operations and monitoring | Hosting, monitoring and support |
| Changes | Vendor compatibility, your mapping changes | Flow and connector updates | Code changes when an API changes |
| Failure recovery | What the app provides | What the platform provides | Whatever you build |
Frequently asked questions
Can engineers see Salesforce case details without a Salesforce licence?
Some apps are designed for this. Check what each copies into Jira.
Does the MuleSoft Jira connector work with Jira Data Center?
No. The Anypoint Connector for Jira "is only for the Cloud version of Jira" (MuleSoft).
Can we start small?
Yes. Escalate cases to Jira and return only the status updates agents need, then add comments, other objects or richer sync.
Sources and currency (4), last checked 19 October 2026
- Atlassian Marketplace listings, including the archived Jira Cloud for CRM page
- Atlassian Support and developer documentation, including the Service Cloud integration
- MuleSoft documentation (Anypoint, Composer)
- Salesforce developer and admin documentation
Getting your Salesforce and Jira integration right
Integrations go wrong on decisions, not code. We help decide what each system owns, then configure and test it.