FormWhisper
Log inStart free
All templates

Bug report template

Reproducible bug reports from people who have never heard the phrase "steps to reproduce".

For product, support, and open-source teams.

Use this template Try it first

Free account. It copies into your dashboard as a draft you can edit.

The 6 questions

  1. 1What went wrong?Long text · required
  2. 2What did you expect to happen instead?Long text
  3. 3Where did it happen?Single choice: Signing in, Dashboard, Billing, Mobile app, Somewhere else · required
  4. 4How much is this getting in your way?Single choice: I can't work at all, I have a workaround, It's just annoying · required
  5. 5What device and browser were you using?Short text
  6. 6Your email, if you'd like to hear when it's fixedEmail

Why it's built this way

Reproduction steps in plain words

Most people can't write repro steps, but they can tell you what they did right before something broke. The follow-up asks exactly that.

Severity in the reporter's words

"I can't work at all" versus "it's just annoying" is easier to answer honestly than P1 to P4, and it maps neatly onto your triage levels.

A follow-up, start to finish

What went wrong?

The export button doesn't work
Follow-up

What were you doing right before it happened, and does it happen every time?

Filtered the table to last month, then clicked Export. Works fine without the filter.

Saved in the what_happened column

Export fails only when a date filter is applied

Follow-ups are a Pro feature. The template ships with them off and with this guidance filled in: "Follow up on 'what went wrong' to get reproduction steps: what they clicked right before, and whether it happens every time."

Report a problem

Sorry something broke. Tell us what happened and we'll take it from here.

6 questions · about 2 min · it may ask a short follow-up

Answer it like a respondent would. In the preview, follow-ups come from a script; the live form writes its own.

More templates