Example context. Preview only. Nothing is submitted.
When to sendSomeone encounters an unexpected behavior they can describe or repeat.
- 01
Report a problem
Establish the concrete mismatch: what happened and what should have happened belong together.
See the questions
- Give the issue a short title
- Make the issue recognizable in a triage queue.
- What happened?
- Capture the concrete failure, including an error message if available.
- What did you expect to happen?
- Describe the expected outcome beside the actual outcome so they can be compared.
- 02
Recreating the problem
Keep useful steps even when a bug happens only sometimes. If the person is unsure how to repeat it, ask what happened just before the problem.
See the questions
- Can you make it happen again?
- Distinguish a reproducible failure from an intermittent event before requesting instructions.
- What steps led to the issue?
- Keep the same steps field for repeatable and intermittent bugs. Do not force a reporter to invent reliable instructions.
- What were you doing just before it happened?
- Ask for the last action when repeatable steps are unavailable.
- 03
A little context
Leave environment and an evidence link until the end. Neither should prevent someone from reporting a problem.
See the questions
- Browser, device, and app version
- Record enough context to narrow differences between machines.
- Link to a screenshot or small example
- An optional link to a small example or screenshot can reduce back-and-forth. Do not include sensitive material.
Using the answers
Try the steps in the reported environment and consider the impact. An intermittent or incomplete report can still describe a serious bug; investigate rather than automatically closing it for missing steps.
When to choose another form
Reporting a security vulnerability. Use your private security reporting channel.
Before you publish
Send reports to an owned triage queue. Provide a separate private channel for security vulnerabilities.
If the app supplies environment details, let the reporter correct them: the bug may have happened on another device.