Skip to content

TFVC Integration with VersionOne and ServiceNow

TFVC Integration

The integration of Team Foundation Server Version Control (TFVC) Integration with VersionOne and ServiceNow provides the project management team complete traceability for any ticket (incident, problem, or defect) raised by a customer.

Download Datasheet Contact Us

TFVC VersionOne and ServiceNow 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 TFVC, VersionOne, and ServiceNow bring rich functionalities to the ecosystem. When TFVC is integrated with VersionOne and ServiceNow, 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 TFVC – VersionOne – ServiceNow 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 workitems in VersionOne and ServiceNow by automating the state transition on TFVC commit

With TFVC, VersionOne, and ServiceNow integration, enterprises can:

TFVC VersionOne ServiceNow Integration

How OpsHub Integration Manager integrates TFVC, VersionOne, and ServiceNow

OpsHub Integration Manager integrates TFVC, VersionOne, and ServiceNow – each system with the 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 VersionOne can be tracked from VersionOne itself. For example, for each commit that development team makes in TFVC, TFVC synchronizes a ‘commit entity’ linked to the specific requirement id back to VersionOne. The support team, using ServiceNow is also up-to-date with the status of a ticket (incident, problem, or defect) raised by a customer.

Popularly synchronized entities

TFVC VersionOne ServiceNow Entities Mapping

Use Case: TFVC integration with VersionOne and ServiceNow

Problem statement: Lack of commit traceability means development and support teams must manually update their systems after successful commit against a workitem.

Solution: If VersionOne, TFVC, and ServiceNow are integrated using OpsHub Integration Manager, the build results will be automatically synchronized to all the integrated systems.

  1. A support team member logs an incident in ServiceNow.
  2. The development team traces it as a ‘defect’ in VersionOne.
  3. The development team works on the ‘defect’ in VersionOne and commits the changes against the ‘defect’ in TFVC.
  4. OpsHub Integration Manager synchronizes the commit information to VersionOne with the associated defect.
  5. The change also reflects in ServiceNow.
TFVC Integration with VersionOne and ServiceNow

Benefits of integration for TFVC, VersionOne, and ServiceNow

TFVC users

  • Each commit can be traced back to its respective workitem at any given point in time from TFVC itself
  • Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits

VersionOne users

  • Traceability for business requirements throughout the ALM tool chain
  • Direct visibility into customer issues and their priorities
  • No dependency on manual communication

ServiceNow users

  • Access and real-time updates to the development status within ServiceNow
  • Easy to categorize and transfer customer tickets to development team
  • No dependency on manual communication