Jira and Salesforce integration

Whalesync syncs Jira and Salesforce both ways. Cases and feature requests from Salesforce become Jira issues, and each issue's status, dates, and release come back to Salesforce.

Jira
Salesforce
Use cases

What you can do with Jira and Salesforce

Support engineers

Escalate cases to engineering in Jira

Sync Salesforce cases into the Jira project your engineers keep for escalations. Each case arrives as an issue with its subject, description, and priority, and engineers work it on their own board. The issue key and its status category, To Do, In Progress, or Done, sync one way back to the case, so the support agent can tell the customer where the fix stands.

Syncs CasesIssues (one table per project)
Each row is a Salesforce case with an issue of its own in Jira. The issue key and engineering status come from Jira.
Product and sales

Log feature requests in Salesforce, plan them in Jira

Reps record each request on a custom object in Salesforce, linked to the account that asked. Each one becomes an issue in the product team's Jira project, with the customer's name in a field of its own. As product moves it through the workflow and gives it a due date, the request in Salesforce shows both.

Syncs Custom ObjectsIssues (one table per project)
Each card is a feature request from Salesforce, with the customer that asked. The column is its Jira status, which syncs back to the request with the due date.
Sales and customer success

Show Jira's release dates in Salesforce

Jira's versions sync one way into a Releases object in Salesforce, with each version's release date and whether it has shipped. When product sets a fix version on a request's issue, the request in Salesforce links to that release, so an account executive can give a prospect a date without asking engineering.

Syncs VersionsCustom Objects
Each row is a version from Jira, synced one way into a Salesforce custom object. Jira's version list is read-only to Whalesync.
What syncs

Everything that syncs

Each card is something you can sync between Jira and Salesforce.

  • Jira Issues (one table per project) Two-way
  • Jira Users Into Salesforce
  • Jira Sprints Into Salesforce
  • Jira Versions Into Salesforce
  • Salesforce Accounts Two-way
  • Salesforce Contacts Two-way
  • Salesforce Leads Two-way
  • Salesforce Opportunities Two-way
  • Salesforce Tasks Two-way
  • Salesforce Campaigns Two-way
  • Salesforce Campaign Members Two-way
  • Salesforce Cases Two-way
  • Salesforce Users Two-way
  • Salesforce Profiles Two-way
  • Salesforce Record Types Two-way
  • Salesforce Custom Objects Two-way
Step-by-step guide

How to sync Jira and Salesforce

Step 1: Open a new sync

In Whalesync, click New sync and choose Jira and Salesforce.

Step 2: Sign in to Jira with Atlassian

Authorize the Jira connector by signing in with your Atlassian account, then pick the Jira Cloud site. Each project you can browse there is a table. Whalesync works as that account, so choose one that can create issues in the projects you sync: a project's custom fields show up only for an account that can. A project admin is best, since Jira lets only an admin's edits skip the watcher emails.

Step 3: Authorize Salesforce

Authorize the Salesforce connector with a Salesforce login, ideally an admin's, because Whalesync sees only the objects and fields that user can. Check Use sandbox to try the sync on a sandbox first. The org needs API access, which Enterprise, Unlimited, and Performance editions include and Professional Edition gets as an add-on.

Step 4: Add the fields, then map

Whalesync can't create fields in Jira or Salesforce, so add the ones the sync will fill before you map. On a case, that might be a text field for the Jira key and an Engineering status picklist with the values To Do, In Progress, and Done. Then pair Cases, or your custom object, with its Jira project, and map the subject to the issue's summary, which Jira requires.

Automap suggests the other pairs: an AI model matches fields by their names and types, without reading any records, and you keep, change, or add to what it proposes. Set the direction field by field, so that Jira's key and status category flow only into Salesforce. A project's table holds every issue in it, subtasks included, so give the sync a project of its own, or a filter that keeps the other issues out.

Step 5: Match cases to existing issues and go live

If some cases already have issues, match them on a field both sides hold, such as the Jira key a case already stores. Before anything moves, the preview counts what Whalesync will create in each app. Then turn the sync on.

Compare

3 ways to connect Jira and Salesforce

  • MuleSoft Composer for Salesforce

    Best when your org already licenses Composer, and flows that create or update an issue when a case changes are enough.

    • Built by Salesforce, with Jira triggers and actions to build flows from (MuleSoft)
    • A license of its own, for Enterprise, Unlimited, and Performance Edition orgs (MuleSoft)
    • Leaves out fix versions, components, and several custom field types, user pickers among them (MuleSoft)
  • Zapier

    Best when you want one-off steps, such as a comment on the Jira issue whenever its case is updated.

    • Starts from events like a Jira status change or an updated Salesforce record (Zapier)
    • Can add comments and work logs to Jira issues, which a sync leaves out
    • Each Zap runs in one direction, and Zapier says it can't do two-way syncing
  • Whalesync

    Best when support, sales, and engineering each stay in their own app, and the fields they share have to agree.

    • One sync, with each field set to flow both ways or one way
    • Jira's users, sprints, and versions come along as tables to link to
    • Priced by the cases, issues, and other records in sync, with unlimited updates

MuleSoft Composer for Salesforce and Zapier checked against their own pages in November 2026.

FAQ

Frequently asked questions

Does Jira integrate with Salesforce?

Yes. Salesforce's MuleSoft Composer, licensed on its own, has a Jira connector for building flows, Zapier runs one-way automations, and Whalesync syncs the two apps both ways. The Atlassian Marketplace also lists connector apps built by Atlassian partners.

Can I create Jira issues from Salesforce cases?

Yes. Pair Cases with a Jira project, map the case's subject to the issue's summary, and each case becomes an issue with the fields you map. The sync runs both ways, so an issue created in that project, subtasks included, becomes a case unless a filter keeps it out.

Can Salesforce change a Jira issue's status?

Yes, when the project's workflow has a transition from the issue's current status straight to the new one, which Whalesync makes. A move that takes more than one step in the workflow shows up as a sync issue, and the issue stays where it is in Jira.

Do Jira comments and attachments sync to Salesforce?

No. Whalesync syncs an issue's fields: the summary, the formatted description, dates, priority, sprint, versions, and the custom fields on the project's create screens. Comments, attachments, work logs, and links between issues stay in Jira.

Does the Jira Salesforce sync run in real time?

No. Neither Jira nor Salesforce notifies Whalesync of changes, so an edit in one app reaches the other when Whalesync next checks that app. Salesforce is reread every couple of minutes, and a large org takes longer to read.

Will Jira email watchers when Whalesync edits an issue?

Not if the Jira account you connect is an admin of the project. Whalesync asks Jira to skip notifications for its edits, and Jira allows that only for project admins, so with any other account watchers get Jira's usual emails. New issues and status changes notify people the way the project is set up to.

More integrations

Other apps to connect

Connect your tools in minutes