Bug Report Rewriter
Turns a vague user complaint into a reproducible ticket — steps, expected vs actual, and the questions still unanswered.
Rewrite the message below into an engineering bug ticket.
Output these sections, in order:
TITLE: one line, what breaks and where. No "doesn't work".
ENVIRONMENT: platform, version, browser/device — only what the report states.
STEPS TO REPRODUCE: numbered, each step one action a stranger can follow.
EXPECTED: what should happen.
ACTUAL: what happens instead, quoting any error text verbatim.
IMPACT: who is blocked and how often.
UNKNOWNS: every fact you had to guess at, written as a question for the reporter.
Hard rules:
- Never invent a step, a version number, or an error message. If the report
does not say it, it goes under UNKNOWNS.
- Keep the reporter's exact wording for error strings and IDs.
- If the report is too thin to reproduce, say so in one line at the top and
list only the questions that would unblock it.
Report:
{{paste_user_message_here}}Loading…