Salesforce Jira Integration: Methods, Setup Steps and Pitfalls
You can connect Jira and Salesforce with a native option, an app from the Atlassian Marketplace, an iPaaS tool, or a standalone integration platform such as ZigiOps. Choose by sync direction, custom field support, hosting and pricing model. This guide compares the methods, lists the ZigiOps setup steps and covers the pitfalls to avoid.
Ways to integrate Jira and Salesforce
Each method differs in direction, custom field support, hosting and pricing. Figures for other vendors come only from their own public pages, linked below; anything those pages do not state is marked “not stated”.
| Method | Direction | Custom fields | Hosting | Pricing model |
|---|---|---|---|---|
| Native Atlassian or Salesforce options | Atlassian: bidirectional, for Jira Service Management with Salesforce Service Cloud (Atlassian page). Salesforce: MuleSoft Composer Jira connector; direction not stated (Salesforce page) | Not stated | Not stated | Atlassian: bidirectional integrations are available in Jira Service Management Premium and Enterprise. Salesforce: not stated |
| Atlassian Marketplace apps and Salesforce AgentExchange (formerly AppExchange) apps | Two-way for Exalate, Appfire and OpsHub; AgentExchange apps: not stated | Yes: custom fields are mapped (Exalate, Appfire) and synced (OpsHub); AgentExchange apps: not stated | Exalate and OpsHub work with Jira Cloud; Appfire works with Jira Cloud, Server and Data Center; AgentExchange apps: not stated | Exalate: per item in sync. Appfire and OpsHub: commercial licence; AgentExchange apps: not stated |
| iPaaS tools | Not stated on the Workato or Zapier (Jira Software Server page) pages | Not stated | Not stated | Not stated |
| ZigiOps | One-way or two-way, per scenario | Yes: any field, including custom fields, is mapped | ZigiWave-hosted cloud or your own infrastructure; nothing is installed inside Jira or Salesforce | Per workflow, from €500 a month, billed yearly; cloud hosting, implementation and a free proof of concept are included |
How to set up the integration with ZigiOps
These steps follow the ZigiOps Jira Salesforce integration guide. No scripting is needed at any stage.
- Check the prerequisites: a running ZigiOps instance, a Jira integration user with project permissions, a Salesforce administrator (or a user with “Modify All Data” and API access), a Salesforce Connected App for the Client ID and Client Secret, correlation custom fields in both systems, and a license that includes the Jira-Salesforce pair.
- Add Salesforce: in Connected Systems choose Add New System, then Salesforce. Enter the instance URL, username, password, Client ID and Client Secret, save, and run Test Connection. Objects and fields are downloaded automatically.
- Add Jira: in Connected Systems choose Add New System, then Jira, and run Test Connection. Jira Cloud connects with OAuth 2.0 and Jira Data Center and Server with Basic authentication; see the Jira connector docs.
- Create or load a workflow: in Configurator choose Add New Workflow and load a template such as Salesforce Cases to Jira Tasks or Jira Tasks to Salesforce Cases, or start a custom workflow.
- Select the entity pair, for example Salesforce Case with Jira Issue or Task. For two-way sync, configure one action that creates and updates Jira records and one that updates Salesforce records.
- Configure correlation: map a field in each system that stores the other record’s identifier, so updates match existing records instead of creating duplicates.
- Map the fields: Subject to summary, Description to description, and Priority and Status with conditional mapping. Map Salesforce Closed to Jira Done through the Jira transition ID. Sync comments with an author filter to prevent echo loops.
- Set triggers and filters: use the poller (a configurable schedule; the default is every 1 minute), the web listener, or both. Add filters such as priority or record type, and optional expressions to transform values.
- Test, then activate: run the workflow in test mode on a non-production record, check the Activity Log and the payloads, then set the workflow to Active.
Pitfalls and best practices
Most Jira Salesforce integrations are rebuilt because of planning gaps, not technology. The six pitfalls below cause most of the rework.
- Undefined scope: agree what should and should not sync before you configure anything. Document trigger conditions, field mappings and which system wins when both change.
- Inflexible connectors: point-to-point connectors often need scripts for custom fields. Check that the platform loads each system’s schema dynamically and maps custom fields in the UI.
- One-way sync: it leaves one team with stale data. Confirm that two-way sync covers comments and attachments, not just top-level fields.
- Overly broad triggers: syncing every case or issue floods both systems. Start narrow, for example by priority, case type or escalation flag, and widen as usage shows the need.
- Schema changes: Jira and Salesforce both change often. Use a platform that reloads schemas, and test the integration in a sandbox before major releases.
- Security and data governance: ask whether the platform stores data in transit. If you work under GDPR or internal data classification requirements, check this before you choose a tool. ZigiOps does not permanently store the data it transfers, and ZigiWave is ISO 27001 certified.
Watch: connecting Salesforce to Jira
Related pages
See what ZigiOps syncs on the Jira Salesforce integration page and browse Jira Salesforce integration use cases. For all connectors, see the Jira integrations and Salesforce integrations pages. To try it, book a demo or start a cloud trial.
Frequently asked questions
How do I connect Jira and Salesforce?
You can use a native option, an app from the Atlassian Marketplace, an iPaaS tool or a standalone platform such as ZigiOps. With ZigiOps, you add Jira and Salesforce as connected systems, load a template such as Salesforce Cases to Jira Tasks, map the fields and test the workflow before activating it. No scripting is needed.
Can Salesforce cases create Jira issues automatically?
Yes. ZigiOps provides a bi-directional template, Salesforce Cases to Jira Tasks, and any Salesforce entity can be paired with any Jira issue type. Filters and triggers decide which cases create issues, for example by priority or record type.
Does Jira Salesforce sync work both ways?
Yes. Each scenario can be configured as one-way or bi-directional. For two-way sync, a workflow has one action that creates and updates Jira records from Salesforce and one that updates Salesforce records when Jira changes. Comments and attachments can sync in both directions.
Which Jira authentication does ZigiOps use?
Jira Cloud connects with OAuth 2.0: you sign in with your Atlassian account and approve the ZigiWave app, so no API token is needed. Jira Data Center and Server connect with Basic authentication. See the Jira connector docs.
Which Salesforce versions are supported?
ZigiOps supports all Salesforce versions and all deployment types. For Jira, it supports Jira Software and Jira Service Management 7.x or newer on all deployment types. See the Salesforce connector docs.
How often does ZigiOps sync?
The sync interval is configurable, as short as 10 seconds. ZigiOps can poll the source system on a schedule, listen for data pushed by a webhook, or use both together.