Assigning tickets to External Approvals

The external approval is given based on chosen change Management Instance which will manage the approval (available options are JIRA for issue tracking, and ServiceNow for change management).

Select the required Override Group from the dropdown. If its required to create a ticket automatically then select the Auto Create Ticket field. Click the Save button to save the changes.

For Issue Tracking Systems, the approval is created based on ticket(s) referenced on the build request. This is either through ticket number references in SCM commit messages, or references on the build request (either through the FlexDeploy application UI, or via the REST API). When the build (project version) is submitted for deployment, the associated ticket is used to link to the approval. When the ticket is approved in the external system, the FlexDeploy approval task is automatically approved.

For Change Management Systems, the approval is created based on the ticket(s) associated to the deployment request. This association is either through a reference on the deployment request (either through the FlexDeploy application UI, or via the REST API), or due to auto-creation configured at the folder level. When the ticket is approved in the external system, the FlexDeploy approval task is automatically approved.

Tickets can also be assigned to packages.

Pipeline Approvals

Similar configuration can defined for External Approval Gates within a pipeline. When using pipelines, the CMS configuration defined on folders or projects are ignored, since the configuration is used from the External Approval Gates themselves. See Creating/Editing a Pipeline Version for details regarding the External Approval Gate.