A good bug report form collects what an engineer needs to reproduce the issue: a summary, the severity, the steps, what should have happened and what did, and a screenshot. Qwenvo's free Bug Report Form template has all six, and it takes a minute to fill in.
What the template asks
- Short summary: a required one-liner. This becomes the title of the ticket.
- Severity: a dropdown with Blocker, Major, Minor and Cosmetic. Four levels are enough to sort a backlog.
- Steps to reproduce: a required long answer. The most valuable field on the form.
- Expected vs actual behaviour: a required long answer. It forces the reporter to say what they believed would happen.
- Screenshots (optional): a File upload block. Files can be up to 1 GB, so a screen recording is fine.
- Your email (optional): so you can ask a follow-up question without forcing contact on anyone.
Fields I would add
- App version and browser or device: as hidden fields filled from the link, so users do not have to guess.
- User or account ID: a hidden field too. See hidden fields.
- How often does it happen?: Always, Sometimes or Once. Intermittent bugs need different handling.
- Is there a workaround?: a short answer. Some of your users have found one.
Wording to copy
- Summary: "In one sentence, what went wrong?"
- Steps: "List the steps that lead to the problem, starting from a fresh page. One step per line."
- Expected vs actual: "What did you expect to happen? What happened instead?"
- Severity: "How badly does it affect you? Blocker means you cannot continue."
- Thank-you page: "Thanks for the report. We triage every one, and we will email you if we need more detail."
Logic ideas
- If the severity is Blocker, require an email, so someone can reach the reporter quickly.
- If the severity is Cosmetic, hide the steps question and make it optional.
- If the reporter says the bug happens on mobile, show a device model question.
- Put a Link block at the top that points to your known-issues page, so common bugs are not reported twice.
See the conditional logic guide for how to set rules up.
Send reports where engineers work
Linear is one of the built-in integrations, so reports can go straight to your tracker. Slack and Discord alert the channel. Google Sheets, Notion and Airtable hold a log. Jira and GitHub are not on the built-in list, so for those use Zapier, Make, a webhook or the REST API.
AI triage adds a category, a priority, a sentiment and a one-to-two-sentence summary to each report, for up to 10,000 submissions a month. A routing rule sends urgent priorities to up to five email addresses or a Slack incoming webhook. Engineers still decide what is a real bug and what it is worth. Read AI form triage.
Mistakes to avoid
- Making every field required. People abandon, or write "n/a".
- Letting users pick severity with no definitions. Say what Blocker means.
- No steps field. "It is broken" is not a report.
- A silent form. Confirm that the report was received, and say what happens next.
- Collecting secrets. Tell people not to paste passwords or tokens into screenshots.
Why this beats a shared inbox
A bug report by email arrives as a paragraph. A form turns it into columns you can sort by severity, filter by version and export as CSV, JSON or XLSX. Partial submissions, free here and a Pro feature on Tally at $29 a month, also show the reports people started and gave up on, which usually means the form asked for too much.
A fair limit
Qwenvo is a form builder and not an in-app bug reporter. It cannot capture console logs or a session replay automatically, so the report depends on what the person types and uploads. For embedded in-product widgets, see a dedicated tool; for collecting well-structured reports from a link or help page, this is enough.
Questions people ask
What should a bug report include?
A summary, the severity, steps to reproduce, expected and actual behavior, and a screenshot or recording.
Can I create a Linear issue from a form?
Linear is a built-in integration, so you can send submissions there. For Jira or GitHub, use a webhook, Zapier or Make.
Is the bug report form free?
Yes, along with every template and feature. See pricing.
Every feature, $0, no card.
Use the bug report template