Page Comparison

Ticket Number Pattern

No

Pattern of the issues within the issue tracking system, used to associate FlexDeploy builds with particular issue(s). If not specified here, the pattern will need to be defined on each project which associates to your issue tracking system.

For Jira, the pattern of tickets is the key is the Jira project Key, followed by a dash (e.g. "MYPROJ-"). All tickets created for this project are prefixed by this key, making it the pattern.

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.

For Azure Boards, the pattern of tickets is the Azure DevOps project name, followed by a dash (e.g. "MYPROJ-").

For GitLab, the pattern must be the project name (not case sensitive), followed by a dash (e.g. "MYPROJ-")

You can provide more than one pattern as comma-separated values.

Update Tickets on Build

No

Check this box if you want to globally update any tickets associated to FlexDeploy builds. Can be overridden at project level.

Build Update Comment Pattern

No

Applicable only if Update Tickets on Build is checked. 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. Can be overridden at project level.

Update Ticket Status on Build

No

Applicable only if Update Tickets on Build is checked. Check this box if you want to globally update the status of any tickets associated to FlexDeploy builds. Can be overridden at project level.

To (Build)

No

Applicable only if Update Ticket Status on Build is checked. Any associated ticket will be updated to this status whenever the build completes successfully. Can be overridden at project level

For GitLab, this must be a transition status (e.g. Reopen, Close) which is valid as a state event in the GitLab Issue API, and not a current status as shown in the GitLab application.

Update Tickets on Deploy

Check this box if you want to globally update any tickets associated to FlexDeploy deployments. Can be overridden at project level.

Deploy Update Comment Pattern

Applicable only if Update Tickets on Deploy is checked. 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. Can be overridden at project level.

Update Ticket Status on Deploy

Applicable only if Update Tickets on Deploy is checked. Check this box if you want to globally update the status of any tickets associated to FlexDeploy builds when they are deployed. Can be overridden at project level.

To (Deploy)

Applicable only if Update Ticket Status on Deploy is checked. Any associated ticket will be updated to this status whenever the deployment completes successfully. Can be overridden at project level

For GitLab, this must be a transition status (e.g. Reopen, Close) which is valid as a state event in the GitLab Issue API, and not a current status as shown in the GitLab application.