Azure DevOps Server (Formerly known as TFS)
- 2010, 2012, 2013, 2015(up to Update 3), 2017, 2017(Update 2), 2018, 2019, 2020
Azure DevOps Services (Formerly known as VSTS)
- Till Fuji Patch 5, Geneva Patch 7, Helsinki,Istanbul, Jakarta, Kingston, London, Madrid, New
York, Orlando, Paris, Quebec, Rome
Azure DevOps – 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, cross-functional collaboration helps the teams get complete context of the business requirements.
Best-of-breed systems such as Azure DevOps (Both Azure DevOps Server and Services, also known as TFS and VSTS) and ServiceNow bring rich functionalities to the ecosystem. By integrating Azure DevOps with ServiceNow, enterprises can diminish collaboration barriers between Development and Customer Service teams that otherwise lead to quality issues, delivery delays, and financial loss.
How Azure DevOps – ServiceNow integration is beneficial for an enterprise
- Real-time access to customer issues and priorities
- Communication on the workitems from the native systems itself
- Real-time updates when a customer issue is resolved
With Azure DevOps + ServiceNow integration, enterprises can:
How OpsHub Integration Manager integrates Azure DevOps and ServiceNow
OpsHub Integration Manager integrates Azure DevOps (Both Azure DevOps Server and Services, also known as TFS and VSTS) and ServiceNow 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 ‘tickets’ from ServiceNow automatically synchronize to Azure DevOps and all the entities and details associated with the ‘tickets’ synchronize back to Azure DevOps.
Popularly synchronized entities
Use Case: Azure DevOps integration with ServiceNow
Problem statement: The Support team receives a ticket from a customer, identifies it as a ‘problem’, and shares the details of the ‘problem’ with the development team via email. Three days later, a support team representative writes a follow-up email to the development team to check the status of the ‘problem’. The development team, then, updates the support team representative that the ‘problem’ was resolved two days back.
Solution: When Azure DevOps and ServiceNow are bi-directionally integrated using OpsHub Integration Manager, the status of the ‘problem’ would automatically change in ServiceNow as soon as its status is changed to ‘resolved’ in Azure DevOps.
- Multiple customers log tickets in ServiceNow citing similar Skype-related issues.
- The Support team identifies these tickets and reports them as a ‘problem’ to the backend team.
- OpsHub Integration Manager synchronizes this ‘problem’ as a ‘bug’ in Azure DevOps.
- The Backend team examines the defect and requests the service team for more information to resolve the bug.
- A customer support representative provides the requested information to the backend team.
- The Backend team then provides a resolution for the ‘bug’ and marks the status of the ‘bug’ as ‘resolved’.
- The status of the ‘problem’ in ServiceNow also gets updated to ‘resolved’. The resolution provided by the backend team appears as a ‘comment’ in the comment section.
Benefits of integration for Azure DevOps and ServiceNow users
Azure DevOps users
- Traceability for business requirements throughout
the ALM tool chain
- Visibility into customer issues and priorities
- No dependency on manual communication for
- Access to the business requirements and associated updates from within ServiceNow
- Easy to categorize and transfer customer tickets to ServiceNow
- No manual efforts needed to keep backend teams updated on customer issues and priorities