Aldorock apps for Zendesk

Ticket Cloner

Clone the ticket you are on into one or more new tickets, with its fields, tags and comments, and edit everything before anything is created.

Getting started

  1. Install Ticket Cloner from the Zendesk Marketplace and choose which agents and groups may use it.
  2. Open a ticket. The app is in the apps panel on the right. The form is already filled in from the ticket.
  3. Edit what the clone should be different: subject, requester, group, assignee, priority, type, tags and custom fields.
  4. Click Clone ticket. The new ticket opens, or, with several clones, the app lists links to all of them.

What is copied

From the ticketHow
SubjectAs shown in the form. With several clones, numbered "(1 of 3)", "(2 of 3)" and so on.
Requester, group, assignee, priority, type, tagsAs shown in the form. Find another requester by name or email. The assignee list shows the assignable agents of the chosen group (no light agents); without a group, or for a very large group, find the agent by name. Changing the group clears an assignee who is not in it.
Custom fieldsEvery active field on the ticket's form: text, multi-line, number, decimal, date, checkbox, drop-down, multi-select and regex fields. Credit card fields are never copied (Zendesk only returns a masked value). Untick "copy" to leave one out. Tags that belong to drop-down and multi-select options follow the field: change the value and the clone gets the new option's tag, not the old one.
Brand and ticket formThe clone uses the same brand and form.
CommentThe first comment, the latest comment, or all comments joined into one, each with its author, time and "(internal note)" where it was one. Images pasted into a comment are replaced by "[Image not copied: name]". A comment longer than about 60,000 characters is shortened, with a last line saying how much was left out.
AttachmentsNot in version 1.0. See below.

Internal note or public reply

The clone's first comment is an internal note or a public reply; you choose per clone. With Keep internal notes private on (the default), text copied from an internal note never goes out as a public reply: if the copied text includes an internal note, the clone starts with an internal note even when you chose public, and the form tells you so. An admin can turn public clones off completely.

Cloning several times

Set Number of clones from 1 to 20. Clones are created one after the other; if Zendesk refuses one, the app stops, shows why and lists the ones already created. Fix the problem and click Create the remaining N: only the missing clones are created, with the same numbering. Solving the original and opening the clone wait until the whole batch exists.

Problems and incidents

On a problem ticket, Link clones as incidents is on by default: each clone is created as an incident of the problem. When you clone an incident that belongs to a problem and the clone stays an incident, it is linked to the same problem.

Solve the original, open the clone

Solve this ticket after cloning sets the original to solved and adds a one-line internal note naming the clones. If Zendesk refuses (for example a required field is empty), the clones stay and the app says why the original was not solved. Open the clone after creating it opens the first clone in a new tab.

Settings

Admins find these under Admin Center โ†’ Apps and integrations โ†’ Zendesk Support apps โ†’ Ticket Cloner.

SettingEffect
Default comment to copyfirst, latest (default) or all. Agents can change it per clone.
Clone comment as internal note by defaultOn by default. The form starts with Internal note.
Allow public clonesOn by default. When off, every clone starts with an internal note.

Errors

When Zendesk does not accept a field, the message appears under that field in plain words, for example "Must be an agent" under Assignee. "Your role does not allow this" means your role cannot create tickets for other requesters or set a field; light agents and some custom roles have limits on which tickets and fields they can create. When Zendesk limits requests, the app waits as long as Zendesk asks (at most 10 seconds) and tries once more; if Zendesk still refuses, it says so and you click again after a minute.

Attachments

Version 1.0 does not copy attachments. Zendesk apps run in the browser and cannot move files between tickets, and private attachments need authenticated downloads. Version 1.1 adds attachments through a small Aldorock server that streams each file from the original ticket to the clone without keeping it; it will be an opt-in setting.

Data

The app runs in your browser inside Zendesk and uses your own Zendesk session. It reads the ticket, its comments, ticket fields and forms, groups and agents, and creates tickets with your permissions. Ticket fields, groups and group members are kept in the browser tab's session storage for up to 10 minutes. Aldorock receives and stores no ticket data.

Language

The app uses the agent's Zendesk language where a translation exists and English otherwise. Version 1.0 ships in English. Text the app writes into tickets (comment headers, the solve note) is kept short.

Frequently asked

Does it keep the original created date or history?

No. A clone is a new ticket created now, by you. Triggers and automations run on it as on any new ticket.

Is the requester notified?

A clone with a public reply notifies the requester the way your triggers do for new tickets. Internal-note clones do not reach the requester.

Does it replace Zendesk's own clone app?

It covers the same job and adds editing before create, comment choice, privacy control, several clones at once and problem links. You can run both while you switch.

Changelog