The Issue Tracking System tab allows association of the folder with any Issue Tracking System Instance which was configured in the topology. You must create the instance prior to configuring your projects.
...
You may wish to have a different Post Deploy status in each environment. To override settings for certain environments, click Add Environment.
Field Name | Required | Description |
|---|---|---|
Ticket Number Pattern | No | Pattern of the issues within the issue tracking system, used to associate FlexDeploy builds with particular issue(s). For Jira, Azure Boards, GitLab, and GitHub, the pattern of tickets must be the project Key, followed by a dash (e.g. "MYPROJ-"). In Jira, all tickets created for this project are prefixed by this key. For other providers, this key isn't part of the ticket id in the external system, but is necessary in FlexDeploy for identifying the project name. For Redmine, the pattern can be whatever you like. Recommended is 'refs #, references #, and IssueID #', as these match the defaults for referencing issues in commits defined by Redmine. You can provide more than one pattern as comma-separated values. |
Post Build Comment | No | The value of this property is a groovy script which evaluates to the comment you wish to update associated tickets with when a build completes successfully. Groovy variables available to the script are provided in the (x=) dropdown to the right. |
Post Build Status | No | Any associated ticket will be updated to this status whenever the build completes successfully. |
Post Deploy Comment | No | The value of this property is a groovy script which evaluates to the comment you wish to update associated tickets with when a deployment completes successfully. Groovy variables available to the script are provided in the (x=) dropdown to the right. |
Post Deploy Status | No | Any associated ticket will be updated to this status whenever the deployment completes successfully. |
Click Save to apply any changes.