Microsoft Azure DevOps is the collaboration platform at the core of Microsoft's application lifecycle management solution, and used by Development and QA teams collaborating with the Microsoft development ecosystem. TFS has features for Task Management, Test Case Management and Agile Planning and Collaboration.
Polarion Connector for Microsoft Azure DevOps connects Microsoft Azure DevOps with Polarion by enabling bi-directional synchronization of work items. Thanks to a seamless integration, disparate teams can collaborate without having to leave their respective work environments. This connector is designed to work both with local (Azure DevOps Server - formerly TFS) and cloud (Azure DevOps - formerly VSTS) solutions.
Here are some scenarios where Polarion Connector for Microsoft Azure DevOps can help:
- Your product and project management teams are using Polarion for managing requirements, while your development teams are using Microsoft Azure DevOps for actual development and testing. You want to give your engineers direct access to all requirements, and at the same time provide your project managers with direct visibility of the development status.
- Your product and QA teams are using Polarion for managing requirements and test specifications, while your Development teams are using Microsoft Azure DevOps for actual development. You want to give your engineers direct access to requirements and defects, and at the same time provide your product team with direct visibility into the development and defect status as well as with direct access to information to create compliance reports necessary.
FEATURES AND BENEFITS
Perform bi-directional and uni-directional synchronization of any artifact type including critical ones like requirements, user stories, tasks, defects and tests. This ensures that all collaborators can see the same data, no matter what application they use.
- Bi-directional synchronization allows the data to flow in two directions. You want your teams to be able to modify the data in their own environment, and then propagate the changes between Polarion and Microsoft Azure DevOps.
- Uni-directional synchronization allows the data to flow in only one direction. For example your Business Analysts create requirements in Polarion, and make them visible, but not modifiable, for the Development team working in Microsoft Azure DevOps.
All details of the artifacts can be synchronized, including links and attachments. This ensures a comprehensive and undiluted understanding of the artifacts, while the respective teams can keep working in their familiar environment.
One of the major advantages of the Polarion Connector for Microsoft Azure DevOps is end to end traceability. Work item types are synchronized together with their links. Any type of relationship is maintained.
You can see what has been built, track the impact of an actual change, or analyze a potential change.
EASY CONFIGURATION AND ADMINISTRATION
You can manage and configure the integrations directly via Polarion administration. As is characteristic of Polarion’s solutions, the administration is designed with ease of use in mind, enabling less technical users to perform complex enterprise configurations.
To configure the integration you need 3 simple steps:
- Configure the Polarion server and the Microsoft Azure DevOps instance that you want to connect: add the details about the applications that you want to configure, the servers, and the project.
- Choose what work item types you want to synchronize. Polarion Connector for Microsoft Azure DevOps can synchronize any artifact type, standard or custom-defined in the applications.
- Configure the mapping: indicate what fields you want to be synchronized, the direction of synchronization, the transformations and who takes precedence in case of conflict.
DASHBOARD AND MONITORING
The connector configuration page in the Polarion administration shows all configured synchronizations: connected applications and projects, mapped work item types, active and inactive synchronizations.