Feedback
Bug report
Structured the way a developer will read it. Asking for the steps separately from the description is the difference between a report that can be reproduced and one that can't.
- Questions
- 7
- Takes about
- 4 min
- Style
- One page
- Scoring
- None
Free, no card. It lands in your workspace as an editable draft.
Worth knowing
- The welcome screen and the intro text above the first question carry example turnaround times, policies and promises. Rewrite them as yours before you publish — they are the part respondents take literally.
What's in it
Report a bug
Welcome screen
A good report is one somebody else can reproduce. List the steps in order, starting from w…
Rich text
- 1
One line: what's broken?*
Short text
- 2
What did you do?*
Long text
- 3
What did you expect to happen?*
Long text
- 4
What happened instead?*
Long text
- 5
Browser and device
Short text
- 6
Screenshot or recording
File upload
- 7
Where should we reply?*
Email
Thanks
Ending
How to use this template
Open it as a draft
Press "Use this template" and it lands in your workspace as an editable form with all 7 questions already in it. No card, and nothing is published until you say so.
Cut what you do not need
Every question you remove is one fewer reason to abandon the form. It takes about 4 minutes to fill in as it stands, and that is the number worth protecting.
Add from the question bank
Pick what you are missing from the questions below. Drag any of them in, change the wording, and use conditional logic so people only see the ones that apply to them.
Share it, or put it on your own site
Publish to get a link, or embed it in a page you already have. Answers arrive in your dashboard, and you can send them on to anywhere else with a webhook or an integration.
32 bug report form questions to choose from
A bug report is only worth filing if someone can reproduce it. The difference between a report that gets fixed this week and one that sits in a backlog for a year is almost always the steps.
These are the questions that get you a reproducible report without making a frustrated user write an essay.
What happened
- What were you trying to do?
- What happened instead?
- What did you expect to happen?
- What is the exact error message?
- When did it happen?
- Is it still happening now?
- Has it happened before?
- Did anything change just before it started?
Reproducing it
- What are the steps to make it happen?
- Does it happen every time?
- What is the URL where it happens?
- Is there specific data that triggers it?
- Does it happen with a different account?
- Does it happen in a different browser?
- Does it happen on a different device?
- Does it happen for other people?
The environment
- Which browser and version?
- Which operating system?
- Phone, tablet or computer?
- What is your screen size, roughly?
- Are you on a VPN or a corporate network?
- Do you have ad blockers or extensions running?
- Is your connection fast or slow?
- What is your account email?
Impact and evidence
- How badly is this affecting you? (Blocked, slowed, cosmetic)
- How many people does it affect?
- Is there a workaround?
- Have you lost any data?
- Attach a screenshot.
- Attach a screen recording if you can.
- Paste anything from the browser console.
- Can we contact you for more detail?
Bug Report form questions, answered
- What information should a bug report include?
- Steps to reproduce, what was expected, what happened, and the browser and device. Everything else is optional. A report without steps is a complaint, and gets treated like one.
- How do I get users to write good bug reports?
- Ask the questions for them. Nobody writes 'steps to reproduce' unprompted, but almost everyone can answer 'what were you doing when it happened'. Separate fields beat one big text box.
- Should a bug report form allow file uploads?
- Yes, and make it optional. A screenshot resolves ambiguity that paragraphs cannot, but a required upload turns away the person reporting from their phone.
- Can bug reports go straight into our issue tracker?
- Yes. A webhook or an integration can create the issue where your developers already work, with the browser and steps already filled in.
- Is this bug report form template free?
- Yes. Use it, publish it and collect answers on the free plan with no card. Paid plans add things like payments, scheduling, removing our badge and your own domain, but none of them are needed to run this form.
- Do I need an account to use it?
- You need one to edit and publish, because the form has to live somewhere and the answers have to come back to you. Signing up takes about a minute and does not ask for a card. The people filling your form in never need an account.
- Can I change the questions?
- All of them. The template is a starting point, not a fixed form: add, remove, reword and reorder anything, change the look, and use logic so people only see the questions that apply to them.
- Can I put it on my own website?
- Yes. Embed it in a page you already have, or share the link. On a paid plan you can serve it from your own domain so the address says your name rather than ours.
- Where do the answers go?
- Into your dashboard, where you can read, search and export them as CSV. You can also have each response emailed to you, pushed to another tool with a webhook, or sent to a connected integration.
- How long does this form take to fill in?
- About 4 minutes as it stands, across 7 questions. Every question you cut brings that down, and shorter forms get finished more often.
Worth reading next
- 30 Customer Feedback Questions That Get Real AnswersQuestions grouped by what you are trying to learn, and the wording changes that stop people giving you polite nothing.
- 18 Survey Question Types, and When Each One Earns Its PlaceMultiple choice, scales, matrices, rankings and open text, with the specific failure mode of each and how to avoid it.
- What to do with two hundred open text answersThe most valuable question on most forms is the one nobody reads, because reading it properly takes an afternoon nobody has.
Others in feedback
Customer feedback
A rating, the reason behind it, and permission to follow up.
Net Promoter Score
The standard NPS question, with the follow-up that makes it useful.
Customer satisfaction (CSAT)
One satisfaction question, asked straight after the interaction.