Move a ticket to another stack
Filed in the wrong place, or a support question that turned out to be a bug? Move the ticket to the right stack without retyping it.
Sometimes a ticket starts in one stack and belongs in another: a support question that turns out to be a bug, or a repair that grew into a project. Move it instead of copying it by hand.
Move it
- Open the ticket and click ⇄ Move at the top.
- Under Move to, pick the stack. You'll only see stacks you can add tickets to.
- Under Start at, pick the step it should begin at in that stack (the first step is chosen for you).
- Check What happens to the fields, then click the Move to button.
The ticket opens in its new stack with a new number there, like PJ-12.
What comes along
- Everything that happened: comments, files, history, the requester and watchers all stay with the ticket.
- Fields that match: a field carries over when the new stack has one with the same name (and, for a dropdown, the same choice).
- Fields that don't: nothing is lost. Their values are written into the new stack's first long-text field under "From RP-1:", or saved in an internal comment if it doesn't have one.
Good to know
- The old link still works. It forwards to the ticket's new home, so links in old emails keep working.
- It's a real move. The step it starts at runs its automatic actions and emails, just like any other move.
- History shows it, like "moved it from Repairs (RP-1) to Projects (PJ-1)."
- Archived tickets need restoring before they can move.
Related
- Moving ticketsMove a ticket to its next step from the ticket page, the board, or Today's Stack, and what happens when you do.
- Working a ticketEverything on a ticket page: the step, owner, due date, fields, files, comments, watchers, tags and history.
- Ticket fieldsEvery field type, when to use each, and how Required, help text and requester visibility make better tickets.
Still stuck? Email hello@ticketstacker.com. A real person reads every message.
