Bug Report Form template
Collect reproducible steps, expected behavior, and the environment where a problem occurred. Copy the accessible markup, adjust the fields, and publish it with Core Forms.
What your visitor sees
Plain semantic HTML rendered through the same default form theme Core Forms applies on the front-end. Try it — this demo confirms inline and sends nothing.
Demo only. On your site, the same markup wires into the normal Core Forms action loop — email, Slack, Google Sheets, webhook, whatever you configure.
The HTML behind it
Copy this block, paste into Core Forms → Add New Form → Fields tab, save. Field names map to merge tags automatically in your action templates.
<p><label for="br-email">Email</label><input id="br-email" name="EMAIL" type="email" autocomplete="email" required aria-required="true"></p>
<p><label for="br-summary">Short summary</label><input id="br-summary" name="SUMMARY" type="text" required aria-required="true"></p>
<p><label for="br-steps">Steps to reproduce</label><textarea id="br-steps" name="STEPS" rows="6" required aria-required="true"></textarea></p>
<p><label for="br-expected">Expected result</label><textarea id="br-expected" name="EXPECTED" rows="4" required aria-required="true"></textarea></p>
<p><label for="br-actual">Actual result</label><textarea id="br-actual" name="ACTUAL" rows="4" required aria-required="true"></textarea></p>
<p><label for="br-file">Screenshot or text log <span>(optional, no secrets)</span></label><input id="br-file" name="EVIDENCE" type="file" accept="image/png,image/jpeg,text/plain"></p>
<p><button type="submit">Send bug report</button></p>
What this bug report form template is for
Use it when support needs structured technical detail before triage can begin.
This version asks only for information needed to complete that job. Tell users not to paste passwords, private keys, payment data, or other secrets into the report.
The markup uses explicit labels, useful autocomplete values, and fieldsets for grouped choices. You can edit every line instead of working around a locked template schema.
Every field, and why it's there
| Field | Type | Required | Why it's there |
|---|---|---|---|
email | Yes | Follow-up contact. | |
| Summary | text | Yes | A scannable issue title. |
| Steps to reproduce | textarea | Yes | The shortest repeatable path to the problem. |
| Expected result | textarea | Yes | Defines the intended behavior. |
| Actual result | textarea | Yes | Describes what happened instead. |
| Screenshot or log | file | Optional | Optional evidence with an explicit size/type limit. |
From this HTML to a working form
- 1
Create the form from a template
In Core Forms, add a new form and choose the Bug Report Form starting point, or paste the HTML below into code mode.
- 2
Remove what you will not use
Delete unnecessary fields, update the labels and choices, then set the success message to explain what happens next.
- 3
Test the whole path
Submit the form with realistic data. Verify validation, the saved submission, notification email, autoresponder, and any integration action.
Three upgrades worth considering
Show fields only when needed
Keep the first view short and reveal follow-up questions from an earlier answer.
Use conditional logic →Route the submitted data
Send the result to email, a CRM, a spreadsheet, or a signed webhook after validation.
Explore integrations →Check the funnel
Measure starts, successful submissions, and field drop-off after the form has real traffic.
Use form analytics →Bug Report Form template questions
Is this bug report form template free to copy?
Yes. The HTML on this page is free to copy and adapt. Core Forms is required only if you want its WordPress submission handling, inbox, actions, analytics, and other plugin features.
Can I change or remove fields?
Yes. The form is plain HTML. Remove any field you cannot justify, rename fields before collecting data, and keep every label associated with its control.
Does the template save submissions in WordPress?
Core Forms can save successful submissions in its WordPress inbox. Storage is a per-form setting, so you can disable it for forms whose data should not be retained.
Can the form send a confirmation email?
Yes. Add an autoresponder action, map its recipient to the submitted email field, and state what the person should expect next.
How should I test it?
Use realistic valid data, missing required data, a malformed email address, keyboard-only navigation, and a narrow mobile viewport. Also verify every configured action and redirect.
The template is free. The plumbing is the product.
Core Forms turns this HTML into stored submissions, spam-filtered
email, and 30+ integrations. Use
CFLAUNCH for 20% off.