How to Connect Jira Cloud with IBM Engineering Lifecycle Management for End-to-End Traceability

Jira Cloud and IBM Engineering Lifecycle Management (ELM) often sit side by side in the same engineering program: developers work in Jira, while requirements and tests live in IBM DOORS Next and IBM Engineering Test Management (ETM). Keeping those two worlds connected, and proving that connection to an auditor, is where most teams struggle.

In this recorded session, Robert Baillargeon, Product Owner at SodiusWillert, walks through OSLC Connect for Jira Cloud in a demo. OSLC (Open Services for Lifecycle Collaboration) is the open standard that lets engineering tools link to each other's data without copying it. Robert shows how that works in practice, with Jira Cloud and IBM ELM connected through live links, without changing how your teams work.

What you will see in this demo

• Jira defects created directly from ETM. A test engineer logs a failing test step and creates a linked Jira bug without leaving ETM. The Affects Version is filled in automatically from the active global configuration.
• Linking from DOORS Next. Engineers select or create Jira stories from a requirement using standard OSLC dialogs, or drag and drop requirements onto Jira items. Both sides get rich previews.
• The Links Explorer in Jira Cloud. This is a dedicated workspace for reviewing, filtering and creating links. It includes a fixed preview pane, link decorators, and a clear indication of which global configuration each link resolves to.
• Traceability reporting in IBM Report Builder. Jira issues appear as native artifacts alongside DOORS Next requirements. You can build one report showing requirements, the Jira issues that implement them, and their status.
• Administration and process controls. Admins can decide which link types are available on which Jira issue types, and whether users may create or only select linked artifacts. They can also set which Jira type ELM tools should create by default.
• The architecture behind it. Robert explains how the OSLC Connect Broker sits between Jira Cloud and IBM ELM, so your ELM servers don't need to be exposed to the public internet.

Who should watch

• Systems, requirements and test engineers working across Jira and IBM ELM
• Jira and IBM ELM administrators planning a Jira Cloud integration
• Teams currently on OSLC Connect for Jira Data Center who are preparing to move to Jira Cloud
• Program and quality managers who need audit-ready traceability under standards such as ISO 26262, DO-178C or ASPICE