...
Work item number syntax to be used with FlexDeploy depends on underlying issue tracking integration. See Out-of-the-Box Issue Tracking System Configuration for details.
Link by Commit Messages
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.
...
In the below pictures, GLORY- is the work item pattern setup for the project and as if commit message contains GLORY-60 which matches pattern GLORY-, it will be considered as linked work item for build.
...
Another 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-60 10 to indicate Work Item GLORY-60. In this case10. 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.
...
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.
...
Link 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.
...