Helix Core – Jama Connect Integration Overview
In an Application Lifecycle Management (ALM) ecosystem, the choice of systems, and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, cross-functional collaboration brings in collective wisdom to make better decisions, faster.
Best-of-breed systems such as Jama Connect and Helix Core bring rich functionalities to the ecosystem and make the work of the product and development team easier. With Jama Connect and Helix Core integrated within the ecosystem, the product development has real-time visibility into the commits made by the development team. It is also easier for them to enforce authentic commits against each work item, and access the changes/edits made to the commits from Jama Connect itself.
How Helix Core – Jama Connect integration is beneficial for an enterprise
- Track commit volume, track commit trends and edits/changes to commit files in real time
- Enforce authentic commits to make sure each commit is happening against a scheduled and open workitem
With Helix Core + Jama Connect integration, enterprises can:
How OpsHub Integration Manager integrates Jama Connect and Helix Core
OpsHub Integration Manager integrates Jama Connect and Helix Core in a bidirectional manner. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All the details related to a commit made against a work-item in Jama Connect can be tracked from Jama Connect itself. For example, for each commit that the development team makes in Helix Core, Helix Core synchronizes a ‘commit entity’ linked to the specific requirement id back to Jama Connect. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
Popularly synchronized entities
Use Case: Helix Core integration with Jama Connect
Problem statement: The product management team doesn’t have visibility into the commit trends and volume. Lack of commit traceability can also lead to compliance issues.
- The Product Manager creates a ‘business requirement’ in Jama Connect.
- The development team works on the requirement, tests it, and then commits it in Helix Core against the ‘requirement id’ specified in Jama Connect.
- For each commit that happens from the development team, OpsHub Integration Manager synchronizes a ‘commit entity’ linked to the specific requirement id back to Jama Connect. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
Benefits of integration for Jama Connect and Helix Core users
Jama Connect users
- Complete traceability from Jama Connect to source code in Helix Core
- Visibility into the progress of development work, the volume and quality of commits made with full context, in real-time
- Reduced dependency on manual communication to track the completion of a task
Helix Core users
- Each commit can be traced back to its respective workitem at any given point in time from GitHub itself
- Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits