Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Recommended option is to specify work items in commit message is by prefixing by #. For example, you can use #701 to indicate Work Item 701, or #GLROY#GLORY-10 to indicate Work Item GLORY-10. When using # prefix, there is not no need to setup set up 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 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 work items can be added using a comma. Just enter work item number(s) as per appropriate syntax and press separate work items with a comma (,) . It will show up like shown in or by pressing the Enter key. Work items will be displayed as shown in the 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 itemitems. The dropdown only shows previously linked work items. Type the entire work item key to enter a new one.

...