Working a ticket
Everything on a ticket page: the step, owner, due date, fields, files, comments, watchers, tags and history.
A ticket page has everything about one request, so nobody has to dig through texts and emails to find out what happened.
Across the top
- Status and step: where the ticket is. Pick the next step here to move it along. See Moving tickets.
- What to do in this step: the button next to the step shows its instructions, if the stack has them.
- + Add to my day: add it to your list for today (if nobody has it yet, you take it too). See Today's Stack.
- Take it: on a ticket waiting in a queue, become its owner.
- ⟲ History: every move, change and automatic action, with who and when.
The details
- Title, owner and due date. Every ticket should have an owner; that's how work stops falling through the cracks.
- Queue: not sure who'll take it? Put it in a team's or a location's queue instead, and anyone in it can take it. See Put a ticket in a queue.
- The stack's fields. Change anything you're allowed to, then save. TicketStacker warns you if you try to leave with unsaved changes.
- Attachments: add photos and files, and download them anytime. Click a picture, PDF, text file or CSV to open it right on the page (CSVs show as a table); other files download.
Comments and watchers
Talk about the work right on the ticket, and @mention people to pull them in. Choose Internal for your team or Public to share with the requester. See Comments and @mentions.
Watchers get updates without owning the ticket, like a manager who wants to know when it's done. Add yourself or someone else; stop anytime with Stop watching.
Tags sit under the watchers: quick labels like urgent or warranty that you can filter by in any stack. See Tags.
Blocked tickets
If a ticket is waiting for something before it can move on by itself, you'll see Blocked: and exactly what's missing. Fill it in, and it moves.
Archive
Made a ticket by mistake? Archive ticket hides it from lists and reports without deleting anything. Restore ticket brings it back.
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.
- Comments and @mentionsKeep the conversation on the ticket, pull people in with @, and choose what the requester sees.
- Put a ticket in a queueGive any ticket to a team's or a store's queue instead of one person, so whoever's free can take it.
- Today's StackPick what you'll get done today, check it off as you go, and see what your team is working on.
Still stuck? Email hello@ticketstacker.com. A real person reads every message.
