Skip to content

VersionOne Integration with TFVC and ServiceNow

VersionOne Integration

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

Download Datasheet Download

VersionOne TFVC & ServiceNow Integration Overview

In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between thecross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functionalcollaboration helps the teams get complete context of the business requirements.

Best-of-breed systems such as VersionOne, TFVC and ServiceNow bring rich functionalities to the ecosystem. When TFVC isintegrated with VersionOne and Service Now, all stakeholders have real-time visibility into the commits made by thedevelopment team. It is also easier to enforce authentic commits against each work item and access the changes/edits madeto the commit files from VersionOne itself.

Please fill this form to download the datasheet.

Yes, I want to receive newsletters, educational and promotional content from OpsHub including invitations to webinars and other events. I know I can unsubscribe any time.
To learn more, please read our privacy policy.

How VersionOne – TFVC – ServiceNow integration is beneficial for an enterprise

  • Trace the requirement breakdown
  • Get complete context of the business requirement and receive real-time updates when there is a change in the plan
  • Coordinate on the delivery timelines seamlessly with concurrent updates on changes

How OpsHub Integration Manager integrates VersionOne, TFVC and ServiceNow

OpsHub Integration Manager integrates VersionOne and TFVC in abi-directional manner. It ensures that all historical and current data isavailable to each user, in that user’s preferred system, with full context,in real-time. VersionOne users have traceability for each workitem ateach stage of development. On the other hand, TFVC users are alwaysup-to-date on iterations schedule and changes/enhancements made toa customer request.

Popularly synchronized entities

VersionOne TFVC ServiceNow Entities Mapping

Use Case: VersionOne integration with TFVC & 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.
VersionOne TFVC ServiceNow Integration

Benefits of integration for TFVC, VersionOne, and ServiceNow

VersionOne users

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

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

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