Discover our story, vision, and impact.

Get Started wIth 30 Days Free Trial

Blog

How to integrate Salesforce and Jira in 2026(A step-by-step guide)

Salesforce captures customer-facing activities while Jira manages engineering execution. Integrating the systems reduces manual handoffs and improves transparency across teams. This guide covers architectural considerations, mapping strategies, and integration best practices.

Can DOORS and Jira be integrated?

Integrating IBM DOORS with Atlassian Jira bridges the gap between Systems Engineering and Agile Software Development. While systems engineers manage highly structured, regulatory-compliant requirements in DOORS, software teams execute tasks, track progress, and manage sprints in Jira.

A well-executed integration ensures end-to-end traceability, eliminates manual duplication, and maintains data integrity for compliance and audits. With a live, secure, bidirectional, and no-code integration, requirements created in DOORS seamlessly synchronize as Jira issue types such as epics, stories, tasks, and sub-tasks automatically, preserving hierarchy, relationships, and full context across systems.

Video Transcript

The business analyst in IBM Rational DOORS starts by creating a requirement of type Heading (00:42). Under the requirement, a title and a description are added using a rich text field (00:50). OIM automatically synchronizes rich text formatting such as bullet points, bold, underline, italics, subscript, superscript, and others (00:55–01:04). The business analyst also adds an Excel sheet under the section object text (01:07). Once saved, all details—including the RTF description and Excel sheet—are automatically synchronized to Jira (01:13). In Jira, the requirement appears as a task with all details, including formatted description and the Excel attachment (01:22–01:35), and the Remote Link and Remote ID of the DOORS requirement are visible (01:39). The engineer in Jira changes the task status to In Progress and adds a comment for the DOORS analyst (01:45–01:51), both of which bidirectionally synchronize back to DOORS (01:55). In DOORS, the status updates to In Progress, and the comment is visible under discussions (02:02–02:08). The analyst then inserts a picture object in a new requirement of type Heading, adds a title and description (02:15–02:35), and creates another requirement of type Feature, associating it as a child of the original heading (02:35–02:43). The parent–child relationship is checked in Jira, where the feature appears as a sub-task linked to the main task, confirming the relationship is preserved (02:54–03:11). The image added in DOORS is also synchronized and available both as an attachment and within the description in Jira (03:18–03:22). Finally, the engineer marks both the task and sub-task as Done (03:27), and these updates synchronize back to DOORS in near real time, where both the parent requirement and sub-task reflect the status Done (03:36–03:53).

Video chapters

00:42 Creating a Requirement in DOORS

01:07 Synchronizing Rich Text and Attachments to Jira

01:22 Viewing Synced Requirement in Jira

01:47 Updating Status and Adding Comments in Jira

02:02 Status and Comments Synced Back to DOORS

02:16 Adding an Image in DOORS Requirement

02:41 Creating a Parent-Child Relationship in DOORS

03:00 Viewing Synced Parent-Child Relation in Jira

03:18 Image Synchronization in Jira

03:29 Updating Task and Sub-task Status in Jira

03:43 Status Updates Synced Back to DOORS