FlexDeploy issue tracking systems integration (out of box or custom) can be configured globally for use by various Projects. Configurations can be overridden at Project level as well as necessary.
...
Field Name | Required | Description |
---|---|---|
Id | Yes | System generated identifier (read-only). |
Name | Yes | Name of the issue tracking system. (read-only for out of box integrations) |
Description | No | Description of the issue tracking system. |
Ticket Number Pattern | Yes | 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 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-"). You can provide more than one pattern as comma-separated values. |
Java Implementation | Yes | Implementation class issue tracking system integration. (read-only for out of box integrations) |
...
Field Name | Required | Description |
---|---|---|
Update Tickets on Build | No | Check this box if you want to globally update any tickets associated to FlexDeploy builds. Can be overridden at the environment, project, or environment/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 the environment, project, or environment/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 the environment, project, or environment/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 the environment, project, or environment/project level. |
Update Tickets on Deploy | Check this box if you want to globally update any tickets associated to FlexDeploy deployments. Can be overridden at the environment, project, or environment/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 the environment, project, or environment/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 the environment, project, or environment/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 the environment, project, or environment/project level. |
Issue Tracking System Variables
The list of Groovy variables available to use. Can be used at the project level on the Issue Tracking Systems tab or global level under Administration → Integrations → Issue Tracking Systems.
Variable | Description |
---|---|
EnvironmentName | Name of the environment selected when build or deploy is created |
PackageName | Name of the current project package. |
ProjectName | Name of the project. |
ProjectVersion | The version of the project to submit for deployment. |
ReleaseLink | Applicable only for build and deployments on the release level else link will just go to last visited release. FlexDeploy link which redirects to this snapshot on the release dashboard. |
ReleaseName | The release name selected when build or deploy is created. |
ReleaseId | The id of the release selected when build or deploy is created. |
ServerBaseURL | The FlexDeploy server base url defined in Adminstration → System Settings → Server Base URL |
SnapshotId | Applicable only for build and deployments on the release level. Internal id value of Snapshot. |
SnapshotName | Applicable only for build and deployments on the release level. Name of the snapshot (auto generated by date and time when created). |
StreamName | Name of the SCM stream selected when build is created. |
WorkflowRequestor | FlexDeploy user that created the build or deployment request. |
Environment Configuration
...