Manuals / Work Tracking / Chapter 2

A · Tickets · beginner · Week 1 · Chapter 2 of 9

Anatomy of a useful ticket

Title that searches well, context, acceptance/repro, attachments, and owner. Empty description is how work stalls.

Path progress
17%

Step 1 of 2

Story template

Problem, why now, acceptance, test notes, links to design/spec.

Story templateDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Story templatedrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Example

Title: <verb> <object> — <context>
Why: …
Scope / AC:
- …
Out of scope: …
Design / spec: <link>
Test notes: …
Deps: …

Do this now

Fill the template for one upcoming story.

Was this step clear?
Chapter learning outcomes
  • Title craft
  • Context links
  • AC / repro
  • Labels without chaos

Clear these before you leave