Change Ticket is associated with Deploy, Utility, or SyncState request and workflow execution will only happen once change ticket(s) are approved. Reports and other execution details will show link to any associated Change Tickets.
When using Release and Pipelines, you can associate Change Ticket with individual deployment or entire release.
You can also use REST API to initiate deploy or utility requests as well and Change Ticket can be associated using REST API too.
Change Request tickets can also be manually associated See #1 and #2 below. Change Ticket provided in #1 applies to all Project/Packages in Snapshot, whereas #2 can be used to provide individual Change Ticket(s) for Project/Packages.
...
When deploying Project/Package individually, provide Change Ticket(s) on the Deploy Request form for each project. See below. If Change Ticket is not valid, then error will be shown and request will not be submitted.
...
Change Ticket is missing validation
...
Change Ticket number does not exist on the CMS
...