The integration of VersionOne with Subversion and JIRA gives the backend team complete control over the codes being committed in the source code repository. It also creates complete traceability for all workitems in VersionOne. With complete traceability for each workitem in the ecosystem, it is easier for enterprises to fulfil compliance requirements.
VersionOne – Subversion & JIRA 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 VersionOne, JIRA, and Subversion bring rich functionalities to the ecosystem. When Subversion is integrated with VersionOne and JIRA, all stakeholders have real-time visibility into the commits made by the development team. It is also easier to enforce authentic commits against each work item and access the changes/edits made to the commit files from VersionOne itself.
How VersionOne – Subversion – JIRA 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 VersionOne workitem by automating the state transition on Subversion commit
With Subversion + VersionOne + JIRA integration, enterprises can:
How OpsHub Integration Manager integrates VersionOne, Subversion, and JIRA
OpsHub Integration Manager integrates VersionOne, Subversion, and JIRA bi-directionally – all three systems with each other. 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 VersionOne can be tracked from VersionOne itself.
Popularly synchronized entities
Use Case: VersionOne integration with Subversion and JIRA
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 VersionOne, Subversion, 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 VersionOne as a ‘bug’.
- The developer works to resolve the ‘bug’ in VersionOne.
- 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 and the bug in VersionOne.
- The development team using VersionOne, then, commits the changes in Subversion.
- The commit information from Subversion then synchronizes to VersionOne and JIRA giving end-to-end traceability to all stakeholders.
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 VersionOne, JIRA, and Subversion users
VersionOne & JIRA Users
- Traceability for business requirements/defects throughout the ALM tool chain
- Visibility into the volume, quality of commits, and commit trends in real-time
- Each commit can be traced back to its respective workitem at any given point in time from Subversion itself
- Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits