Compatibility

• Applause platform’s Azure DevOps Connector is compatible with Azure DevOps Software version 6.0 or above:
  • Azure DevOps Services
  • Azure DevOps Server 2022
  • Azure DevOps Server 2020
• Both Cloud and Server versions are supported

With any BTS Connection, be sure to thoroughly validate your integration to make sure All Fields and Values are properly matched. Example: Applause may identify Severity level 1 as Low, whereas your company may use level 1 as Critical.

Prerequisites

You’ll need the following in order to complete the Azure DevOps Connector configuration:

1. URL - to your Azure DevOps instance in either format:
   1. https://{organisation}.visualstudio.com/{collection}
      {collection}  = DefaultCollection or any other collection name for the project
   2. https://dev.azure.com/{organisation}/
2. Personal Access Token (PAT)  (reference) - for authentication purposes
   1. PATs always have an expiration date so we suggest to set it to maximum value (1 year)
   2. PAT needs to have following scopes selected:
      1. Work Items > Read, write, & manage
      2. Token Administration > Read & manage
      3. Member Entitlement Management > Read
      4. Graph > Read
3. Project Key - Name of the project where to export Bugs
4. Issue Type - Type of the Work Item to create during export

 

Azure DevOps API Endpoints

If necessary, the following Azure DevOps API Endpoints need to be whitelisted:

• GET _apis/projects
• GET _apis/wit/workitemtypes/{Issue Type}/fields
• POST _apis/wit/workitems/{Issue Type}
• GET _apis/wit/classificationnodes
• GET https://vsaex.dev.azure.com/{organisation}/_apis/userentitlements
• POST /_apis/wit/attachments

 

Azure DevOps Connector

Once the BTS Integration was added, Azure DevOps was selected as the connector type and products were assigned, you’ll be required to provide the following information:

URL

Set your web-based access to Azure DevOps.

Personal Access Token (PAT)

We need to generate a PAT (Personal Access Token) for the service user account. To do so, we'll need to log into ADO with that username/password, then follow the instructions here. As you proceed with the instructions, make sure to do the following:

• On step 4, please set expiration at max which is +1 year.
• On step 5, mark the following access scopes:
  • Work Items (Read, write, & manage)
  • Token Administration (Read & manage)
  • Member Entitlement Management (Read)
  • Graph (Read)

Project Key

This is the key of the prerequisite Azure DevOps project

• Field is case sensitive
• Project must be set on your Azure DevOps instance prior to setting the Connector

Issue Type

This is the default issue type for bugs sent from the Applause platform.

 

Notes and Tips

Note the following hints and tips while setting up the integration with Azure DevOps and hints on BTS general.

General

• Learn more about working with the BTS Connectors as part of setting up the integration between the Applause platform and your Bug Tracking System (BTS) here
• Learn more about integrating with your BTS here

Tags

When using the Tags field on field mapping please note:

• Values are space-separated. You may send multiple labels on each exported issue
• Values may include an Applause issue field to be dynamically populated, as well as plain text for fixed values

Two-way ADO Integration

Learn more about how to set up the Two-way Integration here.