Pathwise

Manuals / Bug Reporting & Advocacy / Chapter 4

A · Craft · intermediate · ~30 min · Chapter 4 of 9

Severity vs priority

Severity = impact on users/system. Priority = order of work. You recommend; product/eng own priority.

Path progress
44%

Step 1 of 1

Impact narrative

Who is hurt, how often, workarounds, blast radius.

  • Sev-1 — blocker / data loss / security / no workaround
  • Sev-2 — major feature broken, limited workaround
  • Sev-3 — partial / annoying / edge
  • Sev-4 — cosmetic / polish
Impact narrativeDrag 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 →Impact narrativedrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Write severity rationale for 3 bugs in two sentences each.

Was this step clear?
Chapter learning outcomes
  • Scales
  • User impact stories
  • Avoiding P0 spam

Clear these before you leave