Perimattic
workflow-itsm

Salesforce Jira Integration - Case to Issue Sync

The ERPPlugs Salesforce Jira integration uses the Jira REST API and webhooks to create issues from Salesforce cases, sync status and comments in both directions and link feature requests to accounts and opportunities. It helps support and product teams share one thread without giving every user access to both tools.

Escalate Salesforce cases to Jira issues and keep status, comments and customer impact in sync between support and engineering.

Jira
Salesforce
5-minute setup30-day money backNo coding required
Overview

What this connector does

Support teams work cases in Salesforce while engineering works issues in Jira. This connector creates Jira issues from cases, writes the Jira key back to the case, and syncs status transitions and comments both ways through the Jira REST API and webhooks. It can also record which accounts and opportunities are linked to a feature request, so product teams can see customer demand with revenue context from the CRM and ERP.

At a glance

Category
workflow-itsm
Capabilities
9
Synced data types
5
Setup time
~5 minutes
Before vs After

What changes when you plug ERPPlugs in

See how automation transforms your Jira-Salesforce workflow.

TaskManual IntegrationERPPlugs
EscalationSupport copies case details into Jira by handEscalated cases create Jira issues with mapped fields and a stored key
Status updatesAgents ask engineers for status in chat before replying to customersJira transitions update the case status automatically
Comment sharingComments are pasted between tools and context is lostAllowed comments sync with author attribution
Feature demandFeature requests are counted in a spreadsheetRequests link to accounts and opportunities directly
Impact dataEngineers lack account value when prioritizing bugsLinked-account value is written to a custom field on the issue
Who It's For

Built for teams that need reliable automation

The Jira <-> Salesforce connector fits into finance, ops, and revenue teams that have outgrown copy-paste — the ones whose month-end close should not depend on a spreadsheet, whose ledger accuracy should not depend on human vigilance, and whose sales velocity should not stall behind an accountant's inbox.

Below are the roles that get the fastest return the moment this connector goes live. If yours is on the list, the payback is typically visible in the first billing cycle.

Support Escalation Manager

Needs engineering status visible on cases so customers get accurate updates without chasing.

Product Manager

Wants to see which accounts and how much revenue sits behind each bug or feature request.

Engineering Lead

Needs well-structured issues from support and does not want to work inside Salesforce.

Architecture & Sync

How data flows and what gets synced

The bridge between Jira and Salesforce, and the exact records that move across it.

Data flow
Jira

Jira

ERPPlugs

ERPPlugs Engine

Salesforce

Salesforce

What flows across
Cases to issuesIssue statusCommentsFeature request linksAffected-customer revenue
Sync details
Data TypeDirectionFrequency
Cases to issuesSalesforce → JiraOn escalation
Issue statusJira → SalesforceOn transition (webhook)
CommentsBidirectionalOn comment
Feature request linksSalesforce → JiraOn link
Affected-customer revenueSalesforce / ERP → Jira custom fieldDaily
Automation

Common automation scenarios

Real workflows this connector automates for you.

When

Agent escalates a case to Engineering

Then

Jira bug is created with case details, and the issue key is saved on the case

When

Jira issue transitions to Done

Then

Salesforce case moves to Pending Customer Confirmation and agent is notified

When

Account is linked to a Jira feature request

Then

Issue custom field is updated with total linked accounts and combined annual value

Capabilities

What's included

Everything this connector automates out of the box, no extra setup required.

Create Jira issues from Salesforce cases with field mapping
Write the Jira issue key and URL back to the case
Sync Jira status transitions to Salesforce case status
Two-way comment sync with author attribution
Link feature requests to accounts and opportunities
Show linked-customer revenue on Jira issues via a custom field
Map priority, component and issue type values
Jira webhook support for near-immediate updates
JQL-based filters to limit which issues sync back
Why It Matters

Key Benefits

What changes for your team once this connector goes live.

One Thread

Support and engineering see the same updates.

Impact-Based Prioritization

Revenue and case counts appear on issues.

Controlled Visibility

Choose which comments cross systems.

No Duplicate Updates

Status flows back to cases automatically.

Free to Try

Try the Jira ↔ Salesforce Connector Free

Start with 1 connector and 100 transactions/month — no credit card required. See real data flowing between Jira and Salesforce inside 5 minutes.

Compliance & Setup

Compliance-ready. Live in minutes.

What you get out of the box for statutory compliance — and the exact steps to go live.

Compliance & Compatibility

OAuth 2.0 authorization for Jira and SalesforceEncryption in transit (TLS)Comment visibility rules to keep internal notes internal

Jira

Jira Cloud (Software and Service Management projects)

Salesforce

Salesforce Service Cloud and Sales Cloud with API access

Setup in Minutes

1

Connect Jira

Authorize ERPPlugs using Jira OAuth and select the projects that should receive escalations.

2

Connect Salesforce

Authorize ERPPlugs via a Salesforce Connected App.

3

Map fields and statuses

Map priorities, issue types, workflow statuses and comment visibility rules.

4

Test an escalation

Escalate a sandbox case, change the Jira status, confirm both sides update, then enable.

7-Day Free Trial

Start free for 7 days — no credit card required

Connect your ERP and start syncing in 5 minutes. Try ERPPlugs free for 7 days — no commitment, no payment details, cancel anytime.

  • Full access to all 150+ ERP connectors
  • Real-time data sync across every integration
  • No credit card required to start
  • 7 days, cancel anytime — no long-term commitment
Keep Exploring

Explore More

Docs, guides, and other ways to get more out of Jira.

Answers

Frequently Asked Questions

Yes, ERPPlugs can write the linked accounts, count of cases and an account value from Salesforce or the ERP into custom fields on the Jira issue. Engineering can then prioritize by customer impact. The fields you choose are the only ones written.

ERPPlugs only syncs comments you allow. You can restrict sync to public Salesforce comments and to Jira comments from selected visibility groups, so internal discussion remains internal. Rules are configured before you enable the sync.

ERPPlugs is built around the Jira REST API and supports Jira Cloud. Data Center support depends on network access and API version and is set up case by case. Confirm your deployment type before starting.

ERPPlugs maps Jira workflow statuses to Salesforce case status values using a table you configure, because workflows differ between teams. Unmapped statuses are ignored rather than guessed. You can also choose to sync status in one direction only.

Get Started

Ready to connect Jira with Salesforce?

Join thousands of Indian businesses automating their ERP workflows with ERPPlugs. Setup takes under 5 minutes.