No-code integration platform for rich bi-directional sync
Zero downtime migration to tool of your choice
Keep Historical Data, Without Slowing Down Your Tools
Migrate or restructure Azure DevOps Instances
Real-time, context-rich data lake for AI or analytics
By Role
Accelerate delivery with clear insights
Transform smarter with a connected digital thread
Confident transitions for every enterprise change
By Initiative
Modernize and move to cloud without disruption
Build a compliant digital thread for complex environments
Build the foundation for smarter AI
By Domain
No-code integration across teams & systems
Enable collaboration between IT, support & business teams
Connect PLM & engineering teams for smarter products
Ensure regulatory compliance from start to release
Explore the latest in technology and best practices
Success stories from the field
Actionable insights for your business challenges.
See solutions in action
Learn, plan, and execute with confidence
Official announcements and updates
Join discussions that drive results
Stay ahead with curated insights
Replacing an ALM system shouldn’t mean losing years of engineering history. Learn why legacy data retention matters, why common workarounds fail, and how purpose-built ALM data archiving helps organizations preserve traceability, compliance, and institutional knowledge after migration.
High fidelity integration can effectively leverage Jama Connect in a multi-tool environment. For example, integrating Jama Connect with ALM tools (Jira, Azure DevOps, and Micro Focus ALM) using OpsHub Integration Manager (OIM) enables transparency and collaboration between product management and development / testing teams with bi-directional synchronization of contextual data in real-time. In this video, we demonstrate how OIM fosters better team coordination and full traceability of requirements across the product delivery life cycle by integrating Jama Connect with Jira, Azure DevOps, and Micro Focus ALM.
Schedule a 30-minute live demo with our integration experts
We’ll now move to the demo, where we’ll demonstrate how OpsHub facilitates requirement collaboration and traceability in a multi-tool ecosystem, with Jama being used for requirements management.
Let’s begin in Jama, where an Epic already exists. The product team will break this Epic into features. Some of the features will be moved to Jira, as they need to be developed by the Java team, while others will move to Azure DevOps, as they belong to the .NET team. All features will be pushed to Micro Focus ALM, as it is the QA tool used for testing.
To get started, I’ll break the Epic into features. The first feature will be titled “The ability to edit customer information via the web portal.” I’ll add more details in the description, attach an image for reference, and assign it to the Java team since they are developing this feature. After saving and closing it, I’ll add another feature for the .NET team, which will be created in Azure DevOps. This feature pertains to the desktop app, developed in Visual Studio and .NET, and will be assigned to the .NET team. After saving it, the Epic will be broken into two features—one assigned to the Java team in Jira and the other to the .NET team in Azure DevOps.
Let’s check if the features have been synced. First, we’ll refresh Jira, where the “editing customer information via the web portal” feature appears with all the details filled in Jama. Next, let’s check Azure DevOps for the feature related to the desktop portal. All necessary details, including the Jama feature ID and a direct URL that links to the Jama feature, are present.
Now, let’s move to OpenText ALM (Formerly known as Micro Focus ALM, HP ALM), where both features are displayed. The QA team will review the features and have a question about the desktop app feature in .NET. They’ll add a comment about the prerequisites needed to configure the desktop app and save it. This comment will be visible in both Azure DevOps (used by the .NET team) and Jama, enabling collaboration across the teams.
At this point, all three teams—QA, development (Java and .NET), and the requirements team—are synchronized. The QA team in Micro Focus ALM is working on creating a plan, while the .NET development team in Azure DevOps is reviewing the feature. Let me refresh the view to ensure the comment from OpenText ALM is visible in Azure DevOps, which it is. The .NET team has also added their own questions, and these will sync back to both Jama and OpenText ALM. Let’s check Jama, where both comments are visible—the one from Azure DevOps about version support and the other from OpenText ALM. The product team will address both comments and add replies, which will be integrated back into Azure DevOps and OpenText ALM, demonstrating real-time collaboration across different tools. Let’s quickly check if the comments appear in Azure DevOps, which they do.
Now, a similar process is happening on the Java side. The Java developers are reviewing the feature and have questions, which they’ll add as comments. We’ll return to Jama and enable native notifications, so the team receives an email whenever there’s an update on the feature. Let’s refresh the view to check if the comment from the Java team appears, and there it is. The product team will address their questions and add a comment, which will flow into Jira, similar to the process we saw with Azure DevOps and OpenText ALM.
Let’s check Jira, where the Java team has answered the question they raised within their own tool, without needing to exchange emails or step out of the tool. This completes the first phase of the demo, which covers requirement refinement when multiple teams work across multiple tools.
We’ll now move to the 2nd phase, where both the Java and .NET development teams start working on the feature. They’ll break the feature into user stories in Micro Focus ALM, write test cases for each user story, and execute the test cases. The results will be synced across Java and other tools, and in the end, all user stories and features will be marked as closed.
Let’s start phase two in Jira, where the Java team will break the feature into user stories. They’ll create the first user story, provide a description, and link it to the feature in Jama using ID demo 145. Similarly, they’ll create another user story, add a description, and link it to the same feature. Now, the feature has two stories under it, both integrated with Jama, giving the requirements team full visibility into the user story breakdown.
The .NET team follows a similar process in Azure DevOps, breaking their feature into user stories. They’ll add titles, details, and images for the desktop app and save them. After creating another story, the two sets of stories will be integrated with Jama. We’ll refresh the view to check if the stories have been created, and we can confirm that they have.
Next, moving to OpenText ALM, where the QA team starts writing test cases for the stories. The QA team has already begun writing test cases for both the desktop app and web portal features. Each test case will be named, described, and saved. Test steps like verifying the update profile button and ensuring that users don’t exceed the character limit in the name field will be added. After adding the expected result, the test case will be saved.
The QA team will link the test cases to the corresponding user stories and create test cases for the .NET feature, verifying the email format. After completing the test case details and adding the expected result, they’ll link it to the .NET feature. More test cases will be created to track test traceability in Jama, ensuring that the requirements team has full visibility into the QA status and health.
Let’s check Jama to see the test case information synced. The expanded hierarchy shows the complete visibility of the feature’s progression, from the initial Epic in Jama, through the creation of user stories, and into the addition of test cases in Micro Focus ALM. The requirements team can see this information and track progress.
Finally, we’ll mark all user stories and features as “Completed”. The Java team will mark their stories as done in Jira and close the feature. Similarly, the .NET team in Azure DevOps will close both the stories and the feature. The QA team will execute the test plan and set the status to “Passed” for all test cases. Returning to Jama, the requirements team will see the updated development and QA statuses. The feature transitions to “Done,” user stories are marked as “Completed,” and test cases are marked as “Passed.”
This completes the demo.
Schedule a 30-minute live demo with our integration experts
