Writing tickets
A ticket is a note to your future self, or to whoever you’re asking to do the work. Things that were obvious when you wrote it are hard to recall a week later, and even more so for someone else, person or minion.
A good ticket does two things:
- Whoever reads it can start without asking questions
- There’s no doubt about whether it’s finished
How big a ticket should be
Section titled “How big a ticket should be”Aim for something that takes one to three days.
A ticket that’s too big sits in Doing for days without moving, and the board can no longer tell you whether it’s progressing or stuck. Split tickets like these:
- The title is “Prepare for…”, “Everything around…” or ”… in general”
- You can’t immediately think where to start
- It has been in Doing for more than a week
Make the pieces children of the original ticket. There are two ways:
- In the original ticket’s details, create new ones with Add a child task (they go into Backlog)
- In an existing ticket’s details, choose the original ticket as its Parent (epic)
Parents and children go two levels deep at most. A child can’t have children of its own, and a ticket that already has children can’t become someone else’s child. If two levels aren’t enough, split the parent into two.
At the other end, a five-minute errand doesn’t need a ticket. Writing it up would take longer than doing it.
Make it say what’s being done, starting with a verb.
| Before | After |
|---|---|
| Website | Change the opening hours on the website for the holidays |
| Newsletter | Send the November newsletter |
| The quote | Send Company A next year’s quote |
The board will hold dozens of cards. Make sure the title alone tells a ticket apart from the others.
Description
Section titled “Description”Write down what the person doing the work needs to know.
- Why it’s being done — once people know the goal, you can leave the small decisions to them
- Useful references — last time’s example, materials to use, files in Drive
- Things to watch out for — what not to do, and when to check in first
You don’t have to fill in all of it. A simple ticket you’re doing yourself can go without a description.
Acceptance criteria (what “done” means)
Section titled “Acceptance criteria (what “done” means)”Acceptance criteria are a checklist of what has to be true for the ticket to be finished. This is the most important part of a ticket.
When it’s vague, the person who did the work thinks it’s finished while the person who asked thinks it isn’t. A minion moves a ticket to Review once it judges that every item is met.
Write it so that everyone reading it reaches the same answer.
| Before | After |
|---|---|
| Make it look good | The start date, end date and discount are in the first paragraph of the announcement |
| Check it properly | The table doesn’t run off the side of the screen on a phone |
| Make it easy to read | Under 800 words, with three headings |
- One thing per item. “A and B are done” becomes two lines
- Three to five items is a good size. If you’re past ten, the ticket may need splitting
- People can tick items off in the details, too. Ticking them as you go shows how far along the work is
Assignee, due date and priority
Section titled “Assignee, due date and priority”- A ticket has one assignee. If two people are doing the work, give each their own ticket. With two assignees, each assumes the other has it, and nothing moves
- Only members of the project can be assigned. If someone is missing from the list, add them in the project’s Members tab
- Changing the assignee doesn’t notify anyone. When you hand work to a person, tell them in chat or a thread
- Only set a due date when there’s a real deadline. If everything has one, you can’t tell what’s actually urgent
- Priority is a marker. The order of work comes from the order of cards within a column. Move urgent work to the top
Discussing a ticket
Section titled “Discussing a ticket”Tickets don’t have a comment section. Talk things over in the project’s threads or in chat. Hover over a card to show a button that copies a tag in the form [task:UUID]. Paste it into a thread or chat and it’s immediately clear which ticket you mean.
Write what you agreed back into the ticket’s description or acceptance criteria. People reading the ticket later only look at the ticket.
Reviewing the board
Section titled “Reviewing the board”A board you write once and leave drifts away from reality. Once a week, for ten minutes, go through it in this order:
- Empty Review. Look at what’s waiting to be checked. Move it to Done if it’s right; if it needs changes, add them to the description and move it back to Todo. Nothing notifies you when a ticket reaches Review, so you won’t know unless you look. If this column backs up, work that should be finished never is
- Look at Doing. A ticket that hasn’t moved for days is too big or stuck on something. Split it, or ask the assignee
- Reorder Todo. Put what’s next at the top. Move anything you’re not doing now back to Backlog
- Skim Backlog from the top. Move what you’ve decided to do into Todo. Delete what you no longer need — but deleted tickets can’t be recovered, so leave anything you want to keep in Backlog
Don’t take on too much at once
Section titled “Don’t take on too much at once”A Doing column full of cards looks busy, but it usually means nothing is getting finished. Finish the ticket you’re on before starting another — that’s the single most useful habit for working with a board. As a rule of thumb, keep no more than two or three tickets per person in Doing.
See only your own work
Section titled “See only your own work”Once there are a lot of tickets, use filters. Click + Filter below the header and choose Assigned to me and Hide Done, and only your own open work remains. You can name and save filters you use often. See Board reference for details.
Related
Section titled “Related”- Board — what a board is, and getting started
- Handing tickets to minions — what to watch for in tickets you give to a minion
- Board reference — the details of views, filters, custom fields and sprints