Reproduction steps.
The numbered sequence of actions that recreates a bug deterministically — start state, exact clicks, exact inputs, exact expected and actual results.
Why they exist
Without repro steps, an engineer cannot fix the bug — they can only guess. "Could not reproduce" is the most common bug-ticket close, and it almost always means the steps were too vague.
A useful template
Start state. Step 1, click X. Step 2, type Y. Step 3, observe Z. Expected: A. Actual: B. Environment: browser, OS, URL.
Frequently asked
What if it is intermittent?
Note the rate ("happens roughly 1 in 5 attempts") and any conditions that seem correlated. Intermittent bugs are still bugs.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free