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 The recommended approach for linking work items with project build is to use by including them in commit message, which will automatically link the work item to any builds of that commit.
Work items are linked to project build only if they are found to be valid based on project’s issue tracking configurations.
...
Note that issue tracking configurations are inherited by sub-folder and projects, this . 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 . If a commit message contains GLORY-60, which matches pattern GLORY-, it will be considered as linked work item for build.
...
Recommended The recommended option is to specify work items item number(s) in commit message messages by prefixing by #. For example, you can use #701 to indicate Work Item 701, or #GLORY-10 to indicate Work Item GLORY-10. When using # prefix, there is no need to set up any Work Item Pattern work item ticket pattern on issue tracking configurations.
...
If the work item number wasn’t included in your commit message , 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 Search and select the work items to link, or enter work item number(s) as per appropriate syntax and separate work items with a comma (,) or by pressing the Enter key. Work items will be displayed as shown in the image below.
...
Add one or more work items . The dropdown only shows previously linked work items. Type by searching and selecting from the list or by typing the entire work item key to enter a new one.
...
Save. Now, all builds and deployments of this package will be linked to these work items.
...