The Change Management System tab allows association of the project with any Change Management Instance which was configured in the topology. You must create the instance prior to configuring your projects. Open a project, and select a Change Management System Instance from the drop down to associate it to the project.
...
- Require Change Ticket for Deployment - When submitting deployment requests user is required to specify a valid ServiceNow CMS Change Ticket number.
- Create Change Ticket on Deployment - When a deployment request is submitted a Change Ticket is automatically created within ServiceNowthe underlying CMS. Use this in conjunction with an External Approval to require an approved CMS Ticket to be entered for deployment requests.
When choosing Create Change Ticket on Deployment you have the option of providing a Groovy expressions which calculate specific fields to set on the generated Change Ticket. See Configure Change Management for details regarding specific fields available for ServiceNow, BMC Remedyforce, 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:
| Field | Description |
|---|---|
| EnvironmentName | The name of the target environment. |
| PackageName1 | The package name requested for deployment. Same as ProjectVersion for full deployments. |
| ProjectName1 | The name of the project requested for deployment. |
| ProjectVersion1 | The project version which was requested for deployment. |
| StreamName1 | The stream from which the project version was built from. |
| WorkflowRequestor1 | The FlexDeploy username which requested the deployment. |
| ReleaseName2 | The name of the Release being executed. |
1 Variables are only applicable when the ticket scope is Project/Package
...
Example Groovy expressions
...