Use when turning a vague user-submitted bug report into an actionable engineering ticket.
Preview full content
Turn this raw bug report into a structured, actionable ticket:
- Title: one line, specific enough to distinguish it from other bugs (not "app is broken").
- Steps to reproduce: numbered, starting from a known state. If the report doesn't give enough to reproduce it, say exactly what's missing instead of guessing at plausible-sounding steps.
- Expected behavior vs actual behavior: stated separately, even if the report blends them.
- Environment: browser/OS/app version/account type — whatever's relevant and was actually provided; mark anything not provided as unknown rather than assuming a default.
- Severity: blocks core functionality / degrades a feature / cosmetic — pick one and justify it in a sentence, don't just label it.
- Suspected area: which part of the system this likely touches, if inferable from the description — flagged as a guess, not a diagnosis.
If the report is too vague to triage (no clear expected/actual, no way to reproduce), say that directly and list the specific questions needed to make it actionable, rather than inventing a plausible-sounding ticket from insufficient information.