Associate Work Items to a Build

Work Items are linked with project build (hence with project version) and then are tracked through deployments to various environments. There are few different options to link work items with project build. Recommended option to link work items with project build is to use them in commit message.

Work items are linked to project build only if they are found to be valid based on project’s issue tracking configurations.

Work item number syntax to be used with FlexDeploy depends on underlying issue tracking integration. See https://flexagon.atlassian.net/wiki/spaces/FD65/pages/10125813711 for details.

Work items are captured and linked to a project build from the source control change logs. The change logs are parsed based on either the Work Item Pattern provided in the project issue tracking configuration or with # prefix. You can define a single pattern or multiple patterns separated by comma.

Note that issue tracking configurations are inherited by sub-folder and projects, this is very easy to view and manage on project issue tracking page.

In the below pictures, GLORY- is the work item pattern setup for the project and if commit message contains GLORY-60 which matches pattern GLORY-, it will be considered as linked work item for build.

Recommended option is to specify work items in commit message is prefixing by #. For example, you can use #701 to indicate Work Item 701, or #GLROY-10 to indicate Work Item GLORY-10. When using # prefix, there is not need to setup any Work Item Pattern on issue tracking configurations.

Link 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.

Multiple Work Items can be added using a comma. Just enter work item number as per appropriate syntax and press comma (,). It will show up like shown in image below.

Once a build is submitted, the build workflow execution will link the work items entered in request form. You can see the description and link to work items in the build and deploy execution rows, and in the Work Items section by clicking the Execution Id link. In addition, if there were more work items found as per change logs, those are linked as well.

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.

Save. Now, builds and deployments of this package will be linked to these work items.

 

The following macros are not currently supported in the footer:
  • style