FlexDeploy ships with an internal Issue Tracking System. This uses numeric work item numbers. Such Work Items can be created using + icon on top right corner or from Work Items page using Create button.

Syntax for FlexDeploy Work Items

FlexDeploy work items are represented as numbers in FlexDeploy. For example, 1801, 1802 etc. These numbers are internal identifiers.

Use copy icon available next to work item number to copy it to clipboard, then you can use with commit message or paste it anywhere else.

Open

Create Issue Tracking Instance

Issue Tracking Instance is already pre-configured for you, so no work is necessary on Integrations page.

Open

Configure Folder or Project for Issue Tracking

Configure FlexDeploy ITS instance as Issue Tracking Instance on your project or parent folder. Issue tracking configurations are inherited by sub-folder and projects. This configuration will allow you to integrate FlexDeploy Work Items with your project builds. See Configure Project for Issue Tracking for more details.

There is no need to setup anything for Work Item Pattern in this case, as you will just use # prefix when referencing Work Item in commit message.

Optionally configure for Comment and/or Status update after build or deploy execution.

Linking Work Items with FlexDeploy Builds

Now you can link FlexDeploy Work Items to project builds. In order to link

• using commit messages - use the format #id. For example, #287. You can use one or more work item numbers in commit message, but it is good idea to have separate commits for each work item.

• manually at build time - just specify work item number(s) on build request form in work items input. For example, 1801. Note that # prefix only necessary with commit message.

• manually with package - just specify work item number(s) on package configuration.

See Associate Work Items to a Build for more information about linking Work Items to builds.

Examples