Clone a stack
Copy a stack's fields, steps, rules and emails into a new stack, in this company or another one you run. Tickets stay behind.
Got a stack that works? Clone it instead of building the next one from scratch: a second location's repair stack, a "Returns" stack based on "Orders", or the same setup in another company you run.
Clone it
- Open the stack and click the ⧉ button next to its name (Admins and stack managers see it).
- If you're an Admin in more than one company, pick where it goes under Copy to.
- Give it a Name and a Ticket prefix (like RPC). If the stack has schedules, tick Bring its schedules too to copy them, switched off.
- Click Clone stack.
The copy opens right away, ready for tickets. If the original was still a draft, the copy opens in the editor as a draft too.
What's copied
- The design: fields, statuses, steps, step rules, automatic actions, step emails and reminders, due-date reminders and stack settings.
- Web form settings. The copy's form starts switched off; turn it on when you're ready. See Web forms.
- Who can see it, and in the same company, the people added to a private stack.
What isn't
- Tickets. The copy starts empty.
- The stack email address. Turn one on for the copy if you want it.
- Schedules, unless you tick Bring its schedules too. Copied schedules start switched off, so nothing is created until you turn them on in the copy's Scheduled tickets. Your plan's schedule limit still applies.
Copying to another company
Some things only make sense in the company they came from, so they're left out, and you'll see a list:
- Set owner actions that name a person (pick someone in the new company).
- Steps that fill in a Person field with someone.
- Webhooks (add them again if the new company should call the same address).
Step emails that used a saved template keep their own copy of the words, so nothing goes missing. After copying, you're switched to the other company so you can see the new stack.
Related
- Statuses and stepsStatuses are the big picture (New, In progress, Done); steps are the real stages inside them. Here's how to set both up.
- Step emails (notifications)Email the requester, owner, watchers or a store's shared inbox when a ticket reaches a step, in your own words.
- More than one companyWork for two businesses, or run a few? One sign-in, a company switcher, and an All companies view.
Still stuck? Email hello@ticketstacker.com. A real person reads every message.
