Azure DevOps Server (TFS) – Jira and GitHub 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, the cross-functional collaboration helps the teams get complete context of the business requirements.
Best-of-breed systems such as Azure DevOps Server (TFS), Jira, and GitHub bring rich functionalities to the ecosystem. By integrating Azure DevOps Server (TFS), Jira, and GitHub, the product development team will have real-time visibility into the defects logged by QA team and commits made by the development team. It is also easier for product development team to enforce authentic commits against each work item, and access the changes/edits made to the commits files.
How Azure DevOps Server (TFS) – Jira – 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
- Eliminate manual effort to close Jira or Azure DevOps Server (TFS) workitems by automating the state transition on GitHub commit
With Azure DevOps Server (TFS), Jira, and GitHub integration, enterprises can:
How OpsHub Integration Manager integrates Azure DevOps Server (TFS), Jira, and GitHub
OpsHub Integration Manager integrates Azure DevOps Server (TFS), Jira, and GitHub – all systems with each other bi-directionally. 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 Azure DevOps Server (TFS) can be tracked from Azure DevOps Server (TFS) itself. For example, for each commit that development team makes in GitHub, GitHub synchronizes a ‘commit entity’ linked to the specific requirement id back to Azure DevOps Server (TFS). Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’. The Project Management team can also view the development progress and commit details from Azure DevOps Server (TFS) itself.
Popularly synchronized entities
Use Case: Azure DevOps Server (TFS) integration with Jira and GitHub
Problem statement: No control on backlogs getting committed – therefore, anyone can commit on a bug which is not even present in the active sprint.
Solution: If Azure DevOps Server (TFS), GitHub, and Jira are integrated using OpsHub Integration Manager, OpsHub Integration Manager will be able to track commits and send notifications to the relevant stakeholders when changes are made to the code base.
- During a Quality Assurance (QA) test, a quality control team member logs a ‘defect’ in Jira. The ‘defect’ also gets synchronized to Azure DevOps Server (TFS) as a ‘bug’.
- The development team receives the ‘requirements’ and starts work on it.
- The developer works to resolve the ‘bug’ in Azure DevOps Server (TFS).
- The quality control team, then, runs a test case against it. The test case passes.
- The quality control team changes the status of ‘bug’ to ‘resolved’. OpsHub Integration Manager, automatically, makes this update to the associated defect in Jira.
- The development team, then, commits the changes in GitHub.
Note: Any change made to the code base before the defect is resolved will be notified to the development and quality control teams, giving them complete control to revert the change.
Benefits of integration for Azure DevOps Server (TFS), Jira, and GitHub users
Azure DevOps Server (TFS) and Jira users
- Complete traceability from Azure DevOps Server (TFS) and Jira 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