The configuration is performed by the Parasoft administrator and only needs to be set up once. 

In this section:

Connecting DTP to Azure DevOps

1. Choose Report Center Settings from the settings (gear icon) menu.
2. Choose External System, click Edit Settings, and choose Azure DevOps from the System type menu.
3. Enable the Enabled option.
4. Enter a name for the server in the Name field. The name is required but does not affect the connection settings or render in any other interfaces.
5. Enter the URL of your Azure DevOps system in the Application URL field. Must include your Azure DevOps collection name.
6. The Display URL field defines the URL which is displayed in Parasoft DTP pages when links to your Azure DevOps system are presented in a web browser. Typically, this should be the same as the above Application URL field, but in some cases it can be different, such as when you work in a reverse proxy environment and links to Azure DevOps from the user's local web browser with Parasoft DTP are different than from the Parasoft DTP server (for example, https://dev.azure.com/<yourorganization>).
7. Enter your username and Azure DevOps API token in the appropriate fields (see Generate Azure DevOps Token below). The login must have sufficient privileges to create Azure DevOps issues in the projects specified in the Project Associations section. 
8. Click Test Connection to verify your settings and click Confirm.
   

Generate Azure DevOps Token

1. Sign into your organization in Azure DevOps (https://dev.azure.com/<yourorganization>).

2. From your home page, open your user settings, and then select Personal access tokens.
   

3. Select + New Token.
4. Name your token, select the organization where you want to use the token, and then choose a lifespan for your token.

5. Select the scopes for this token to authorize for your specific tasks.

   1. Under Scopes, select Custom defined.
   2. Click on the Show all scopes.
   3. Select Test Management and enable Read & write.
   4. Select Tokens and enable Read & manage.
   5. Select Work items and enable Read, write, & manage.
   6. Click Save.
6. When done, make sure to copy the token. For your security, it won't be shown again. Use this token as your password.

Once your Personal access token is created, you can use it anywhere your user credentials are required for authentication in Azure DevOps.

Advanced Configuration

You can modify the ExternalSystemSettings.properties configuration file located in the <DTP_DATA_DIR>/conf directory to change the default behavior of the integration. DTP's out-of-the-box integration with Azure DevOps is configured to use default or commonly used fields and work item types. If you customized your Azure DevOps system, however, then you can configure the settings detailed below to align data in DTP with your custom configuration.

Please note that ExternalSystemSettings.properties is expected to use ISO 8859-1 (Latin1) character encoding. Any character not supported by ISO 8859-1 must be represented in keys and elements using Unicode escape sequences, which is to say a backslash (\) and a lowercase u, followed by the four-digit hexadecimal code for the character. For example, the "En Dash" (–) character (not to be confused with the "Hyphen-Minus" character (-)) is not supported by ISO 8859-1, so it must be represented by its Unicode escape sequence \u2013. As a result, something like example.property.value=Foo – Bar would need to be entered as example.property.value=Foo \u2013 Bar.