Collect bug reports with reproduction steps, environment details, and screenshots: reports your developers can actually act on.
Ready to use
Summarize the bug in one sentence
Short Answer
What steps led to the bug?
Long Answer
What did you expect to happen, and what happened instead?
Long Answer
How severe is it for you?
Multiple Choice
Where did it happen?
Short Answer
Screenshot or screen recording
File Upload
Your email (so we can tell you when it's fixed)
A bug report form that asks the questions a developer would: reproduction steps, expected vs. actual behavior, severity, environment, and a screenshot, turning "it's broken" into a ticket someone can fix without a follow-up interview.
Most user bug reports fail at reproducibility, so this template makes the three reproducibility questions required: the steps, the expectation, and the reality. The severity question (phrased from the user's perspective, not engineering jargon) gives your triage a genuine urgency signal, and the optional email closes the loop, which is what turns reporters into repeat reporters.
Embed it in your app's help menu or link it from your support page. Route submissions via webhook straight into your issue tracker and the form becomes the front end of your engineering queue.
Use webhooks to create issues automatically in your tracker or automation tool, or have your AI agent pull recent submissions and summarize them via Formly's MCP support.
Yes. The file upload field accepts screenshots and screen recordings, which resolve more bugs than any written description.
Allow it; the email field here is optional. A slightly less traceable report beats an unreported bug.
Not an exact fit? Use this template as a starting point and edit anything, or describe what you need and let Formly's AI adapt it for you.
