Settings in Azure DevOps

In addition to the settings on the Testersuite side , the following things need to be set on the Azure DevOps side to make linking work both ways:

1. Creating a Personal Access Token
   Allows work items to be created and modified via the link from Testersuite
2. Creating two web hooks
   Allows changes on the Azure DevOps side to be made to Testersuite

1. Creating a Personal Access Token (PAT)
A PAT is associated with the Azure DevOps user who creates it. This user is then also visible in Azure DevOps as the one making changes to work items through the integration. You could choose to create a special API user for this in Azure DevOps (with the name 'Testersuite Integration', for example). You can read how to do that here:

• Creating a Personal Access Token

2. Creating web hooks in Azure DevOps project(s)
Web hooks allow changes in Azure DevOps to be made to Testersuite. For each Azure DevOps project you want to use in the integration, you need to create two web hooks in the following way:

• Web hook 1: Update work items
• Web hook 2: Delete work items

Once you have completed the settings in Testersuite and the above settings in Azure DevOps, you can start using the link. The first step is to connect a Test cycle to an Azure DevOps project.