Any project, application, or folder can be bound to a configuration management instance, and optionally override the global CMS configuration. . This configuration is used for linking/creating CMS tickets during during adhoc deployment createsdeployments, and can optionally bind an approval to the status of the inked linked ticket. Additionally, pipelines can be decorated with External Approval Gates to create and/or link CMS tickets and bind the gate approval to the status of the underlying ticket.
...
- Require Change Ticket for Deployment - When submitting deployment requests, user is required to specify a valid CMS Ticket number. Use this in conjunction with an External Approval to require an approved CMS Ticket to be entered for deployment requests.
- Create Change Ticket on Deployment - When a deployment request is submitted, a Change Ticket is automatically created within the underlying CMS.
The ticket field values can be set as hard-coded literal values or make use of Groovy variables to decorate the ticket with context for the project/request. See Configure Change Management 9803742444 for details regarding specific fields available for ServiceNow, BMC Remedyforce, and Freshservice Freshdesk, and Jira ITSM.
All Groovy script fields have access to the following variables, and can be selected using the 
drop-down on the right side of the field:
...
Similar configuration can defined for External Approval Gates within a pipeline. When When using pipelines, the CMS configuration defined on folders, applications, 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.