Syntax for Azure Boards Work Items
JIRA issues Azure Boards work items 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.
...
Go to Azure Boards and log in as the user you want to use for FlexDeploy to Azure Boards Integration.
Generate a Personal Access Token in Azure Boards following this guide.
Choose an expiration date based on your security policies. Shorter expiration dates will require updating the ITS more frequently.
Choose the following OAuth scopes to comment on and change status of issues:
Create Issue Tracking
...
Instance
An Azure Boards instance looks like this.
...
Work Item pattern is optional. This , if specified his will used to parse source code commit logs for JIRA Issues, this is explained in next sectionwork item numbers. Alternatively, you can just prefix work item numbers with # in commit message.
Optionally configure for Comment and/or Status update after build or deploy execution.
...
Now you are ready to link Azure Work Items Boards issues with project builds.
Linking by Commit Messages
Set up your FlexDeploy project’s issue tracking configuration with a work item pattern. The pattern must be Azure Boards Project name + “-”. If your Jira project name is Denver, then you can use Denver-1 in commit message as Denver- would be In order to link
using commit messages, use the format #issue for example, #Denver-1. Or you use Denver-1234 in commit message if Denver- is 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.
...
Push and merge your change.
When you create a build, the work item numbers are pulled from your commits.
Linking by Manual Entry at Project Build Time
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 work item number should be Azure Boards Project Name-Number. 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 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 work item. The dropdown only shows previously linked work items. Type the entire work item key to enter a new one.
...
manually at build time - just specify work item number(s) on build request form in work items input. Note that # prefix only necessary with commit message.
manually with package - just specify work item number(s) on package configuration.
See Link Work Items to Project Build for more information about linking Work Items to builds.
Examples
...