Require reproduction steps
A bug report without steps to reproduce is nearly useless. Make 'Steps to Reproduce' required and add a placeholder that shows the expected format.
Free template · 9 fields included
Bug Report Form Template
Standardize bug reports with severity classification, browser details, reproduction steps, expected vs. actual behavior, and screenshot uploads. Collect actionable bug reports — not vague complaints.
No credit cardFree forever planCustomizable fields
Fields included
9 pre-built fields, ready to customize.
#
Field label
Type
Required
1
Reporter Namee.g. Your name
Short text
Yes
2
Emaile.g. your@email.com
Email
Yes
3
Bug Titlee.g. Brief description of the bug
Short text
Yes
4
Severity
Dropdown
Yes
5
Browser
Dropdown
No
6
Steps to Reproducee.g. 1. Go to...
2. Click on...
3. See error
Long text
Yes
7
Expected Behaviore.g. What should happen?
Long text
Yes
8
Actual Behaviore.g. What actually happens?
Long text
Yes
9
Screenshot
File upload
No
All fields are fully customizable — add, remove, or reorder after opening the template.
Use cases
Who uses this template.
Public bug reporting for SaaS products
Internal QA team issue submission
Beta testing feedback collection
Client-facing issue reporting for agencies
Best practices
How to get the most from this form.
Separate expected vs. actual behavior
Two distinct fields — 'What should happen' and 'What actually happens' — force reporters to think clearly about the discrepancy and give developers a clear target.
Use a severity dropdown
A severity field (Critical, High, Medium, Low) lets you prioritize the inbox before reading every submission. Define what each level means in your confirmation message.
Make screenshots optional but encouraged
Screenshots dramatically speed up reproduction. Don't require them (it blocks urgent reports) but make the field prominent and add a clear label.
FAQ
Common questions.
What information should a bug report include?
A complete bug report needs: Bug title, Severity, Browser/OS, Steps to reproduce (numbered list), Expected behavior, Actual behavior, and optionally a Screenshot. This template covers all of these.
Can users upload screenshots in the bug report?
Yes. The bug report template includes a file upload field for screenshots. Files are stored on Cloudflare R2 with 1 GB free on the free plan. Supported formats: JPG, PNG, GIF.
Can I connect bug reports to my project management tool?
Formiqa doesn't have native integrations, but you can export submissions to CSV and import into Linear, Jira, or Notion. For automation, use Zapier or Make to connect Formiqa submissions to your issue tracker.
How do I prioritize incoming bug reports?
The Severity dropdown in this template lets you filter submissions by severity level in your Formiqa dashboard. Export to CSV for more advanced prioritization across large volumes.
Can I add this bug report form to my app's 'Help' menu?
Yes. Publish the form and copy its URL. Add it as a link in your help menu, feedback button, or any in-app support flow. You can also embed it as an iframe in a dedicated support page.
Use this template for free.
All 9 fields included. Customize and publish in minutes.
Related templates
More templates you might need.
4 fields
Contact Form Template
Free contact form template with name, email, phone, and message fields. Ready to publish in seconds. No code required.
View template
6 fields
Survey Form Template
Free survey form template with multiple question types: radio, checkbox, dropdown, and open text. Collect structured responses without a survey platform subscription.
View template
9 fields
User Research Recruitment Form Template
Free user research recruitment form. Screen and recruit participants for interviews and usability tests. Collect role, company size, tool usage, and availability.
View template