Clone Ticket
Clone an existing ticket with configurable options.
Clones an existing ticket, choosing whether to copy fields, links, status, attachments, and add a clone link.
Inputs
- Ticketrequired — Ticket. Selects the source ticket to clone.
- Clone Fields — Boolean. Overrides whether the clone copies field values from the source ticket, and it falls back to the node config when left unconnected. When true, the new ticket inherits the source fields; when false, those values are left behind.
- Clone Links — Boolean. Overrides whether the clone copies linked tickets, and it falls back to the node config when left unconnected. When true, the clone duplicates the source ticket's links; when false, link relationships are not copied.
- Copy Status — Boolean. Overrides whether the clone keeps the source ticket’s status, and it falls back to the node config when left unconnected. When true, the new ticket is created in the same status as the source; when false, it uses the default clone behavior for status.
- Add Clone Link — Boolean. Overrides whether the clone adds a link back to the source ticket, and it falls back to the node config when left unconnected. When true, the clone service creates a clone relationship between the original and the new ticket.
- Copy Attachments — Boolean. Overrides whether the clone copies attachments, and it falls back to the node config when left unconnected. When true, attached files are copied onto the new ticket; when false, attachments are omitted.
Outputs
- Signal — Boolean. Indicates the clone completed successfully and downstream nodes may continue.
- Ticket — Ticket. Returns the newly created cloned ticket when that output is requested.
Configuration
- Clone Fields — Boolean. Controls whether field values are copied into the new ticket by default.
- Clone Links — Boolean. Controls whether existing ticket links are copied into the new ticket by default.
- Copy Status — Boolean. Controls whether the cloned ticket inherits the source status by default.
- Add Clone Link — Boolean. Controls whether the clone operation creates a clone link back to the source ticket by default.
- Copy Attachments — Boolean. Controls whether attachments are copied into the new ticket by default.
Example use cases
Recurring templates
Clone a canonical checklist ticket each cycle with Copy Attachments on so the runbook comes along.
Split work
Clone without copying status to start the duplicate fresh, and enable Add Clone Link to keep the two connected.