Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Creating an OAuth Token for FlexDeploy ITS

  1. Go to Azure Boards and log in as the user you want to comment on Azure Boards Issues with.

  2. Generate a Personal Access Token in Azure Boards following this guide. ​

  3. Choose an expiration date based on your security policies. Shorter expiration dates will require updating the ITS more frequently.

  4. Choose the following OAuth scopes to comment on and change status of issues:

Azure Boards ITS Instances

An Azure Boards instance looks like this:

Supported Azure DevOps API Versions:

5.1-preview, 5.2-preview, 5.3-preview, 5.4-preview, 5.5-preview, 5.6-preview, 5.7-preview, 5.8-preview, 5.9-preview,

6.0-preview, 6.1-preview, 6.2-preview, 6.3-preview, 6.4-preview, 6.5-preview, 6.6-preview, 6.7-preview, 6.8-preview, 6.9-preview,

7.0-preview, 7.1-preview.

Setting Up Folders and Projects to Use the Azure Boards ITS Instance

Then back in FlexDeploy, set up the Issue Tracking settings on your folders and projects.

Linking Azure Boards Issues to FlexDeploy Builds

Now you are ready to link tickets by commit message or by manually entering them on project builds or project packages.

Linking with Commit Messages

Set up your FlexDeploy Project with a ticket pattern. The pattern must be Azure Boards Project name + “-” + issue number.

Following this pattern, make a commit message.

Push and merge your change.

When you create a build, the issue numbers are pulled from your commits.

Linking by Manual Entry at Project Build Time

Issue numbers can also be entered on the build request form to link the issue at build time.

The issue number should be Azure Boards Project Name-Issue Number

Linking Issues to Project Packages

If you are working with a package-based project, you can associate issues with packages that will live through its build and deployment lifecycle.

Add one or more Issues by clicking the edit package button on the right panel. The dropdown only shows previously linked issues. Type the entire issue key to make a new one. The issue number should be in the format Azure Boards Project Name-Issue Number. After saving, all builds and deployments of this package will automatically be associated to that Azure Boards Issue.

  • No labels