The integration of Jama with GitHub ensures completely traceability of all workitems.
With this integration, the product management team can easily track commit trends and volume. With complete traceability for each workitem in the ecosystem, it is also easier for enterprises to fulfill compliance requirements.
Jama GitHub Integration Overview
In an Application Lifecycle Management (ALM) environment, the choice of systems and the collaboration between the cross-functional teams play a great role in delivering quality solutions. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements.
Best-of-breed systems such as Jama and GitHub bring rich functionalities to the ecosystem.
By integrating Jama and GitHub, the product development team will have real-time visibility into the commits made by the development teams. The product development team can also access changes/edits made to the commits from Jama itself in real time. The integration also ensures that only authentic commits can be made against each workitem.
How Jama – GitHub 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 Jama + GitHub integration, enterprises can:
How OpsHub Integration Manager integrates Jama and GitHub
OpsHub Integration Manager integrates Jama and GitHub bidirectionally. 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 can be tracked from Jama itself. For example, for each commit that the development team makes in GitHub, GitHub synchronizes a ‘commit entity’ linked to the specific requirement id back to Jama. 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: Jama integration with GitHub
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.
Solution: If Jama and GitHub are integrated using OpsHub Integration Manager, there will be complete traceability for each requirement in the ecosystem.
- The Product Manager creates a ‘business requirement’ in Jama.
- The development team works on the requirement, tests it, and then commits it in GitHub against the ‘requirement id’ specified in Jama.
- 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. 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 and GitHub users
- Complete traceability from Jama to source code in GitHub
- Visibility into the volume, quality of commits, and commit trends in real-time
- Reduced dependency on manual communication to track the completion of a task
- 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