Bug Report Form
Get a reproducible bug report first time, with the steps, the expected result, and the environment captured in a fixed shape.
Powered by deoochform
Opens in the builder. Nothing is saved until you edit it.
- Fields
- 11 questions
- Theme
- Midnight, switchable in the preview
- Updated
- 11 August 2026
Categories
- Support
- Support Forms
- Bug Forms
- Technical Forms
Ideal for
- Support teams
- Engineering teams
- QA
- Product teams
Best used in
- Issue intake
- Beta testing
- Internal reporting
About this template
A bug report without reproduction steps costs an engineer more time than writing the fix. This form forces the three part shape that makes a report actionable: what you did, what you expected, and what happened instead, each in its own field so none of them can be skipped.
The frequency question is what tells triage whether to chase it. A fault that happens every time can be reproduced in minutes, and one that happened once may be a race condition worth a lot of effort or a browser extension worth none, and knowing which you have changes who picks it up.
Environment questions are kept to browser and device, because a longer list gets abandoned and those two explain most rendering faults. Add a console log field if your users are technical, and route critical severity straight into your on call channel.
Templates are a starting point, not legal or professional advice. Where a form carries consent, medical, or contractual wording, have somebody qualified review it against the rules that apply to you before you publish.
Fields in this template
- Summarise the problem in one line*Short text
- How bad is it?*Dropdown
- Steps to reproduce*Long text
- What did you expect to happen?*Long text
- What happened instead?*Long text
- Does it happen every time?*Single choice
- BrowserDropdown
- DeviceDropdown
- Link to the form or page it happens onWebsite
- Screenshot or screen recordingFile upload
- Email address*Email
Every field can be renamed, reordered, made optional, or removed once the template is open in the builder.
Related templates
Browse all templates- Support Request Form
Support Request Form
Your nameEmail addressHow urgent is this?Critical (I can't work)High (a key feature is broken)Normal (something is wrong)SummaryWhat happened?Screenshot or attachmentChoose a fileTriage incoming issues with the context you actually need: severity, what happened, and a screenshot.
- Refund Request Form
Refund Request Form
Full nameEmail on the orderOrder numberOrder dateWhy you want a refund
ReasonTell us what happenedWhich items are you returning?Photos, if the item is damaged or wrongChoose a fileWhat you would like
Handle refunds without a thread. The order number, the reason, and the evidence arrive together, so a decision takes one look.
- Feature Request Form
Feature Request Form
What would you like us to build?What problem would it solve for you?How do you handle it today?Which part of the product?How much would this matter to you?How often would you use it?Does another product do this well?Email addressPlanCollect feature requests with the problem behind them, so the roadmap gets built from needs rather than from a list of solutions.