A · TicketsBeginner35 min read
2. Anatomy of a useful ticket
Work Tracking · 36 pages source format
Title that searches well, context, acceptance/repro, attachments, and owner. Empty description is how work stalls.
What you'll learn
- Title craft
- Context links
- AC / repro
- Labels without chaos
Story template
Problem, why now, acceptance, test notes, links to design/spec.
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.
Clear?
Bug template
Environment, steps, expected vs actual, evidence, severity guess, regressions.
Do this now
File or rewrite one bug with evidence attached.
Pro tip. One bug per ticket. Split hydras.
Clear?