Jira Salesforce integration: two-way sync without scripts
Without integration, support copies each case into Jira and relays updates by hand.
ZigiOps keeps Salesforce cases and Jira issues in two-way sync, as often as every 10 seconds, without scripts. It is a standalone platform that runs as a ZigiWave-hosted cloud or on your own infrastructure, and it does not permanently store your data. It supports Jira 7.x or newer and all Salesforce versions. A safe test mode checks mappings on real data before go-live. Licensed per workflow, from €500 a month, billed yearly.
Jira 
Salesforce A customer reports an issue to the account team in Salesforce while engineering tracks the fix as a Jira issue. The two records evolve separately, so sales and engineering give the customer conflicting answers.
ZigiOps links each Salesforce case to its Jira issue and keeps them synchronized in real time. Status, priority, comments and account context propagate both ways, so everyone sees the same customer truth.
What manual work disappears
- Re-keying each case as a Jira issue
- Relaying developer status back to the customer
- Copying comments between the case and the issue
- Translating status and priority by hand
- Closing the case when the issue is resolved
What does this handoff cost you?
A quick estimate for this integration.
Illustrative estimate based on your inputs. Not a guaranteed cash saving. Actual results depend on workflow design and volume.
How the Jira ↔ Salesforce mapping works inside ZigiOps
A look at the visual field-mapping canvas ZigiOps engineers use to configure this pair — point, click, connect. No scripts, no pipelines.
Jira 
Salesforce Per field, not per record — if only the priority changed on one side, only that field is resolved, not the whole ticket.
Lock specific fields (e.g. Priority) to always defer to one system, regardless of which side changed last.
Route simultaneous conflicting edits to a review queue instead of silently picking a winner, when that's the safer default.
Jira connector Salesforce connector See the Customer-to-Engineering solution → Every field that matters, mapped both ways
Map Jira entities to Salesforce entities down to the individual field, without writing a script.
Before you book: what you need to know
| Question | Answer |
|---|---|
| Supported versions | Jira Software and Jira Service Management 7.x or newer, on all deployment types. Salesforce: all versions and all deployment types. See the Jira connector docs and the Salesforce connector docs. |
| What syncs | Salesforce cases and Jira tasks, with ready-made bi-directional templates. ZigiOps reads each system's schema dynamically, so any field, including custom fields, can be mapped. |
| Access needed | A Salesforce user plus the Client ID and Client Secret from the Salesforce App Manager. 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. |
| Where it runs | ZigiWave-hosted cloud, or your own infrastructure. |
| Your data | ZigiOps does not permanently store the data it transfers. ZigiWave is ISO 27001 certified. See Security and compliance. |
| Price | Per workflow, from €500 a month, billed yearly. Cloud hosting, implementation and a free proof of concept are included. See pricing. |
| Try it | Start a free trial. A safe test mode validates mappings on real data before go-live, and a free proof of concept is included. |
| Next step | Start a free trial · Book a demo |
More control over how Jira ↔ Salesforce syncs
Updates flow the moment they happen — no polling delays, no scheduled batch jobs.
Scope every sync with filters on priority, record type, project or any custom field.
Built-in logic decides which update wins and logs every decision for full traceability.
Sync resumes on its own after downtime or network interruptions — nothing to restart by hand.
Validate field mappings and rules against real data before the integration goes live.
See sync status and catch failures early, without digging through logs.
When a sync fails, ZigiOps surfaces the likely cause and a suggested fix — no log-diving required.
One customer issue, sales and engineering aligned
A customer reports a problem to their account team in Salesforce while engineering resolves it in Jira. ZigiOps keeps both records telling the same story.
The account team logs a case with priority and the customer's account context.
A mapped Jira issue appears instantly and stays linked to the Salesforce case.
Status and comments sync back to the case, so sales always sees current progress.
The case closes in step with the issue — no conflicting answers to the customer.
Jira ↔ Salesforce FAQ
Is the Jira–Salesforce sync two-way?
Yes. Cases and issues stay aligned in both directions in real time, with conflict-resolution logic keeping both systems authoritative so neither overwrites the other.
What fields map between the two?
Case ↔ issue, status, priority, account ↔ reporter, and comments — all in both directions with full fidelity, fully configurable in the visual editor.
Do I need Apex or Jira automation rules?
No. The entire integration is configured no-code in ZigiOps — no Apex triggers and no Jira automation rules to build or maintain.
Can I connect multiple Jira or Salesforce instances?
Yes. ZigiOps supports unlimited connections between instances, so one Jira project can sync with several Salesforce orgs — or the reverse — each with its own field mapping and rules.
What happens if a case and issue are updated at the same time?
Built-in conflict-resolution logic decides which update takes precedence and logs the decision, so both systems stay authoritative and every change is auditable.
Can I limit the sync to specific cases or issues?
Yes. Conditional triggers let you scope the sync by priority, record type, project or any other field, so only the records that matter cross over.
Which Jira and Salesforce versions are supported?
ZigiOps supports Jira Software and Jira Service Management 7.x or newer on all deployment types. For Salesforce it supports all versions and all deployment types.
How does ZigiOps connect to Salesforce and Jira?
Salesforce connects with a username and password plus the Client ID and Client Secret from the Salesforce App Manager. 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.
Which Salesforce records can be synced with Jira?
ZigiOps ships bi-directional templates for Salesforce cases to Jira tasks and Jira tasks to Salesforce cases. It reads each system's schema dynamically, so any field, including custom fields, can be mapped.
How fast does the sync run?
ZigiOps syncs continuously on an interval you configure, as short as 10 seconds.
How much does it cost?
ZigiOps is licensed per workflow, from €500 a month billed yearly. Cloud hosting, implementation and a free proof of concept are included.
Show us your Jira–Salesforce process.
Book a demo and we'll connect your Jira and Salesforce instances in real time.