Bug Report template

A bug report form that front-loads what engineers need to reproduce the issue: required repro steps, expected-versus-actual behavior, a four-level severity scale, an environment dropdown covering browsers and mobile apps, and attachments sized for screen recordings. Reports that arrive in this shape skip the ping-pong of clarifying emails and go straight to triage.

Use this template Start free — no card

10 questions · works on the free plan (500 responses/month) · fully customizable

File upload question

What’s inside

The questions this template ships with — rename, reorder, or delete any of them in the builder.

01Your emailEmail

02One-line summaryShort text

03Steps to reproduceLong text

04What did you expect, and what happened instead?Long text

05How bad is it?Multiple choice

06Where did it happen?Dropdown

07Link to the page (if applicable)Website

08Screenshot or screen recordingFile upload

When to use this template

The report-a-bug link inside a web app, where the URL field captures exactly which page misbehaved
A public beta collecting structured reports from testers who aren't professional QA
A dev agency giving clients a bug form during UAT so issues arrive with repro steps instead of a phone call
An open-source project whose maintainers want severity and environment attached before an issue is filed

Tips to get more from it

Repro steps are required, and the field's description shows the 1-2-3 format inline. Requiring this one field is the single biggest lever on report quality — resist making it optional even if a few reporters grumble.
The severity options carry their definitions in the option text (data loss, key feature broken, workaround exists, visual only), so reporters self-triage more honestly than with bare Critical/Major labels. The ending screen sets expectations to match — edit both together.
The file field takes up to three attachments at 25 MB each — sized for screen recordings, which resolve where-did-it-break debates faster than any written description.

Questions people ask

What makes a good bug report?

Steps to reproduce, expected versus actual behavior, the environment, and a screenshot or recording. This template requires the first and asks for the rest, which is why reports built on it are triage-ready on arrival.

Can users attach screen recordings to a bug report?

Yes — the upload field accepts any file type, up to three files at 25 MB each, which comfortably fits short screen recordings.

Can I customize the environment list?

The dropdown ships with the major browsers, iOS, Android, and API; add or remove entries in the field editor to match the platforms you actually support.