How teams connect Jira and Salesforce
Pick the setup closest to yours. Salesforce cases and opportunities sync with any native or custom Jira work item type.
-
Bugs
Items sync both ways between Jira and Salesforce
Cases
Escalate customer-reported bugs to engineering
When a case is found in Salesforce, create a matching bug in Jira and keep them in sync.
Status, comments and priority sync both ways, so account teams answer customers from the Salesforce case without asking engineering where the Jira bug stands.
-
Stories
Items sync both ways between Jira and Salesforce
Cases
Turn customer feature requests into backlog items
When a case is found in Salesforce, create a matching story in Jira and keep them in sync.
Status, description and priority stay in sync, so sales and account teams see in Salesforce when the Jira story for a requested feature enters development.
-
Epics
Items sync both ways between Jira and Salesforce
Opportunities
Kick off delivery work when deals close
When an opportunity is found in Salesforce, create a matching epic in Jira and keep them in sync.
Each product on the won opportunity becomes a story under the epic, and description and attachments sync both ways, so engineering builds what sales sold.
Trusted by Fortune 500 companies and global brands
Watch Jira and Salesforce sync both ways
Demo video:
Jira and Salesforce 2-Way Sync
Everything Unito syncs between Jira and Salesforce
Choose which tool creates new items and which way each field syncs, so Salesforce cases can create Jira bugs while status, comments and priority update both ways. Set rules on field values to decide which cases and bugs sync.
Jira
Supported object types
- Tasks
- Sub-tasks
- Epics
- Stories
- Bugs
- + All native & custom work item types
Also syncs
Comments
Attachments
Subtasks
Dependencies
Hierarchies
Rich text
Supported fields
Two-way
- Summary
- Description
- Issue status
- Assignee
- Priority
- Due date
- Start date
- Issue type
- Label
- Affected version
- Blocking
- Comment
- Component
- Environment
- Epic
- Fix version
- Resolution
- Security level
- Sprint
- Story point estimate
- Subtask
- Attachment
- Is blocked by
One-way (read only)
- Reporter
- Time spent
- Project
- Sprint start date
- Issue key
- Original estimate
- Remaining estimate
- Sprint end date
- Created at
- Issue ID
- Link to issue
- Updated at
Supported Jira versions
Salesforce
Supported object types
- Tasks
- Cases
- Contacts
- Accounts
- Leads
- Opportunities
- + All native & custom objects
Also syncs
Comments
Attachments
Subtasks
Hierarchies
Rich text
Supported fields
Two-way
- Subject
- Status
- Priority
- Due date
- Attachments
- Comment
One-way (read only)
- Account
- Related to
- Is closed
- Contact/lead
- Last modified date
- Created
- URL
Two-way
- Subject
- Description
- Status
- Priority
- Case type
- Attachments
- Company
- Contact
- Country
- Asset
- Case origin
- Case reason
- Case source
- Internal comments
- Parent case
- Product
One-way (read only)
- Account
- Last modified by
- Case number
- Closed
- Closed date
- Contact email
- Fax
- Mobile
- Created by
- Created date
- Last modified date
Two-way
- Title
- First name
- Last name
- Assistant name
- Description
- Owner
- Attachments
- Lead source
- Campaign
- Phone
- Salutation
- Assistant phone
- Birthdate
- Business fax
- Business phone
- Department
- Home phone
- Mailing city
- Mailing country
- Mailing state/province
- Mailing street
- Mailing zip/postal code
- Mobile phone
- Other country
- Other phone
- Other postal code
- Other state
- Other street
- Related account
One-way (read only)
- Account
- Related to
- Creation date
- Update date
- Created
- Contact ID
Two-way
- Title
- First name
- Last name
- Description
- Status
- Lead source
- Company
- Country
- Phone
- Salutation
- Annual revenue
- City
- Email bounced date
- Email bounced reason
- Employees
- Industry
- Rating
- State/Province
- Street
- Website
- Zip/Postal code
One-way (read only)
- Full name
- Converted
- Converted date
- Created date
- Last activity
- Last modified date
- Lead ID
Two-way
- Name
- Description
- Stage
- Owner
- Close date
- Type
- Amount
- Forecast category
- Attachments
- Lead source
- Campaign
- Contact
- Currency
- Next step
- Probability
- Total opportunity quantity
One-way (read only)
- Account
- Related to
- Expected amount
- Is closed
- Last modified by
- Last modified date
- URL
Real-time data sync with full control, no coding required
Enterprise-grade sync without the enterprise-grade complexity
Enterprise integration tools handle customer-to-engineering workflows at scale, but they demand certification, scripting, and multi-week rollouts. Unito handles the same workflows between Jira and Salesforce with rules anyone on the team can configure.
Abstracted complexity
Lower total cost of ownership
Scalability and resilience
Enterprise-grade control and reliability
Unito is designed to meet the highest standards of security and performance.
SOC 2 Type 2 certified
GDPR and CCPA compliant
- SSO
- Secure from end to end
- Access controls and flow permissions
- Centralized monitoring tools
- No data stored by Unito
See how teams succeed with Unito
See how you can sync Jira and Salesforce with Unito
Book time with an integration expert who can help solve your specific workflow integration challenges.
What to expect
- A 15-30 min call to assess your workflow and integration needs
- A solutions overview of Unito’s sync platform
- Hands-on help to get started and support your evaluation
Frequently asked questions about Jira and Salesforce
Atlassian’s Salesforce features cover narrower jobs, such as read-only insights in Jira Product Discovery, and Salesforce’s own route is MuleSoft Composer, licensed separately. Unito syncs records bidirectionally. See our Jira + Salesforce integration guide for a full comparison.
No native record sync. Atlassian’s Salesforce features cover narrower jobs: read-only insights in Jira Product Discovery, Service Cloud cases raised as Jira Service Management alerts, and Salesforce data in Rovo search. Salesforce’s route, MuleSoft Composer, is licensed separately.
Bidirectional. Jira summary, status, assignee and priority and Salesforce case subject sync two-way. Flow direction (which tool creates items) and per-field direction are set separately, so even a one-way flow can sync field updates both ways. For most connectors, only new comments sync, not edits.
Yes. Salesforce custom fields on cases, opportunities, and accounts map to Jira custom fields on issues. Direction is per field: account data flows in, sprint status flows back.
Yes. A flagged Salesforce case creates a linked Jira story with priority, description, and account owner carried over. Status, sprint, and resolution sync back to the case, so support knows the moment a bug ships — without leaving Salesforce.
Yes. A closed-won opportunity can create a linked Jira epic, with required-features mapping to stories under it. The hierarchy stays intact in both directions as engineering reorganizes the work.
Yes. Unito connects Salesforce with Jira Cloud, Jira Data Center, and Jira Server through the REST API. Field mapping and flow direction work the same across all three. Salesforce and self-hosted Jira are premium integrations on Enterprise plans; Basic and Pro customers contact Unito to use them.
No engineering or scripting is required. Admins configure sync rules, field mappings, and flow direction through Unito’s no-code interface — the same setup Salesforce admins use to manage field mapping without needing deep Jira administration expertise.
About Jira
Jira is a configurable project and issue tracking platform that allows agile teams to plan, oversee, and manage workflows efficiently. Streamline task management with sophisticated customization capabilities via the Atlassian platform.
Learn more about Unito's Jira integrations ↗Popular Tool Pairings
About Salesforce
Salesforce is the world's leading CRM platform, helping businesses manage customer relationships, sales pipelines, service cases, and marketing campaigns in one unified cloud environment.
Learn more about Unito's Salesforce integrations ↗