...

Syntax for Azure Boards Work Items

JIRA issues are represented as AzureDevOpsProjectName-NUMBER in FlexDeploy. For example, Trial1-10, Denver-2 where Trial1 and Denver are names of Azure DevOps projects. See image below for reference.

...

Preparing for Azure Boards Integration with FlexDeploy

You need to create an OAuth Token for use in FlexDeploy. This token will be entered for Azure DevOps Personal Access Token on Issue Tracking Instance.

...

An Azure Boards instance looks like this:.

...

Supported Azure DevOps API Versions

...

Configure Azure Boards Issue Tracking Instance on your project or parent folder. Issue Tracking configurations are inherited by sub-folder and projects. This configuration will allow you to integrate Azure Work Items with your builds. See Configure Project for Issue Tracking for more details.

Work Item pattern is optional. This will used to parse source code commit logs for JIRA Issues, this is explained in next section.

Optionally configure for Comment and/or Status update after build or deploy execution.

...

Now you are ready to link Azure Work Items with project builds.

Linking

...

by Commit Messages

Set up your FlexDeploy Project project’s issue tracking configuration with a ticket work item pattern. The pattern must be Azure Boards Project name + “-” + issue number. If your Jira project name is Denver, then you can use Denver-1 in commit message as Denver- would be setup as work item pattern.

Alternative you can always just prefix with # and not work item pattern configuration is necessary. For example include #Denver-1 in commit message and Denver-1 work item will be picked up during build.

Following this pattern, make a commit message.

...

When you create a build, the issue work item 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 If you didn’t remember to put the work item number in your commit, and you are building the project manually, you can enter work item numbers at build time.

The issue work item number should be Azure Boards Project Name-Issue NumberNumber. In this example, it’s Denver-2.

...

Linking Issues to Project Packages

If you don’t put work item numbers in your commit message and you are working with a package-based project, you can associate issues work items with packages that will live through its build and deployment lifecycle. Go to the project and package which you wish to link a work item. Edit the package.

Add one or more Issues by clicking the edit package button on the right panelwork item. The dropdown only shows previously linked issueswork items. Type the entire issue work item key to make enter a new one. The issue number should be in the format Azure Boards Project Name-Issue Number. After saving, all

...

Save. Now, builds and deployments of this package will automatically be associated to that Azure Boards Issue.

...

linked to these work items.