Free template · No signup
Bug Report Template
Give your developer a clear starting point: steps to reproduce, what you expected, and what happened instead. Fill in the report below or start from the completed example.
Copy your report as Markdown or download a Word .docx. No email or signup required.
Free bug report form · 3 sections
Write your bug report
Your draft stays in this browser. Copy or download it to share.
Use the template with any issue tracker. Describe the symptom and mark unknowns clearly; a report does not need a confirmed root cause.
Completed example
A website bug report example
A mobile contact form appears to do nothing after submission. This illustrative report records the visible failure, the test conditions, and what remains unknown. The people, site, build, and attachment filenames below are examples.
Issue and environment
- Issue title
- Contact form gives no confirmation after Send on mobile
- Report ID
- BR-101
- Page URL or affected screen
- https://staging.example.com/contact
- Environment and version
- Staging · build 2026.09.06-rc2 Safari on iOS 18.6 · iPhone 13 · viewport 390 × 844 Signed out; other devices and browsers not yet tested
- Reported by
- Alex · QA
- Date and time observed
- 2026-09-06 10:15 UTC
Reproduce the issue
- Preconditions and test data
- Open a fresh tab on the staging site while signed out. Use test data: Alex Test, qa@example.com, and the message 'Please ignore: QA submission'. The required fields are visible and enabled.
- Steps to reproduce
- 1. Open https://staging.example.com/contact. 2. Enter the test name, email, and message in the required fields. 3. Tap Send once. 4. Wait 10 seconds and check the form for a confirmation or error message.
- Expected result
- A successful submission displays 'Thanks, we will be in touch.' If submission fails, a visible error explains what to do next. This is the contact-form acceptance criterion for the release.
- Actual result
- The button responds to the tap, but the form stays on screen with the entered text. No success or error message appears after 10 seconds. Whether the message reaches the server is not yet verified.
- Reproduction frequency
- 3 of 3 attempts after reloading, on the environment above
Triage and evidence
- Severity
- Major: the tested contact flow gives users no confirmation; wider impact is unconfirmed
- Priority
- High: verify before approving this release candidate
- Status and owner
- Needs triage · engineering owner unassigned · QA contact: Alex
- Screenshots, recordings, and error details
- Example screenshot filename: contact-form-after-send.png (form still visible after 10 seconds). Example recording filename: contact-form-mobile.mp4 (fields completed and Send tapped once). No console error was captured. A cause has not been established.
- Impact, workaround, and retest notes
- A visitor may retry or leave without knowing whether the message was sent. Duplicate delivery has not been verified. No tested workaround yet. Retest pending: record the fixed build, browser, and submission result before closing.
Notice the difference between the symptom and a diagnosis: no confirmation appeared, but the report does not claim the server lost the submission. That is a question for the investigation.
How to write a bug report someone can follow
A useful bug template makes the important details easy to find. Atlassian's bug report guidance includes environment, severity, reproduction steps, and expected versus actual results. Use those details to describe a specific observation rather than a general complaint.
Name the observed problem
A developer can identify the feature and symptom from the title.
- Use a title that names the feature, action, and unexpected result.
- Record the page URL or affected screen, reporter, and observation time.
- Check for an existing report and link related issues instead of mixing separate bugs.
Ready when: One issue with a clear title and location.
Record the environment and starting state
Someone attempting reproduction knows which setup was tested.
- Include environment, build, browser version, device, and relevant account role.
- Note login state, required settings, and safe test inputs.
- Mark environments you have not tested as unknown.
Ready when: An explicit setup and the preconditions needed to start.
Write the steps to reproduce
A teammate can follow the sequence without guessing which controls to use.
- Number each action and name the page, field, button, or menu involved.
- Keep the sequence as short as you can while still observing the issue.
- Repeat only when appropriate and record successful reproductions out of total attempts.
Ready when: A specific sequence and an honest reproduction frequency.
Compare expected and actual results
The team can see what failed and what a retest should check.
- Describe the expected behavior and reference the requirement when available.
- Describe the actual behavior using exact messages and observed timing.
- Attach relevant screenshots, recordings, or errors without treating them as proof of a cause.
Ready when: Two separate outcomes supported by available evidence.
Triage, assign, and retest
The bug stays traceable from the first report to a verified outcome.
- Record severity, proposed priority, known impact, and any tested workaround.
- Assign an owner and update the issue status as investigation progresses.
- Retest the original sequence on the changed build and record the result before closing.
Ready when: A tracked issue with a documented verification result.
Write clear steps to reproduce
“The form is broken” leaves the next person to guess. “Open /contact, fill in the required fields, tap Send once, then wait 10 seconds” gives them a sequence to try. Include the account role and test inputs when those change the outcome. A recording adds evidence; the written steps still explain what to do.
Before filing, search for an existing report. MDN's issue-reporting guidelines recommend checking for duplicates and using a clear title and description. Keep a report focused so its outcome is easy to verify.
Severity and priority answer different questions
Severity describes the effect of the bug. Priority describes when the team should address it. Agree on your team's labels and record the reason, because the two values do not always match.
Severity: how much does it hurt?
Describe what users cannot do and whether a workaround exists. A form that prevents contact may be major; a slightly blurry logo may be minor. State the tested scope instead of assuming every visitor is affected.
Priority: what should we do next?
Consider reach, deadlines, workarounds, and the release plan. A small error on tomorrow's campaign page may need attention before a larger issue in a feature that remains disabled. The triage owner confirms the order.
A simple bug tracking template
Use this small bug tracker template to index your reports. Keep one row per issue, with an owner and current status. In your working tracker, link the ID to the full report so evidence and reproduction steps remain one click away.
| ID | Issue | Severity | Priority | Owner | Status |
|---|---|---|---|---|---|
| BR-101 | Contact form gives no confirmation | Major | High | Unassigned | Needs triage |
| BR-102 | Header logo looks blurry | Minor | Normal | Sam | Open |
| BR-103 | Footer contact link opens the wrong page | Moderate | High | Morgan | In progress |
As the list grows, a bug reporting system can manage assignment, replies, and status changes in one place. Keep the same report fields when moving from a spreadsheet into that workflow.
From report to investigation
Capture the page context while you report the bug
With Simple Commenter, a reviewer can pin feedback to an element on the website. Page URL, browser, and viewport context travel with the comment, alongside a screenshot when enabled and available JavaScript errors when capture is on. Your team gets more of the setup without asking the reporter to retype it.
Keep writing the actions you took, expected behavior, and user impact. Captured context supports reproduction and investigation; it does not automatically supply those steps or establish the cause.
Explore visual website feedback1. Keep the evidence together
Read the original comment, screenshot, page details, and available console errors in one place. An error is a clue to investigate, not proof that it caused the reported behavior.
2. Start from an AI dev brief
When available, a developer brief summarizes the website issue and affected element, with a likely fix when supported by the captured context. Review it against the report before acting.
3. Bring the context to your agent
Through the MCP integration, a permitted AI tool can read the feedback and available brief. Code changes need separate repository access. Review and test the result before resolving the issue.
Trusted by 600+ agencies, freelancers, and enterprises
Trusted by Agencies,
Loved by Clients
See why web professionals call Simple Commenter the best website feedback tool, and never look back.
/ Rated 5.0 on Product Hunt & 4.8 on G2
Simple. Effective. Game Changer
@Dsouldiva
Finally, a feedback tool my clients actually enjoy
@craigfenton
A Game-Changer for Web Feedback – Worth Every Penny!
@ryanbarilla
The tool I've been searching for
@alexs89
Simple, yet ingenious
@koen.kerkvliet
Great feedback app and so easy to use!
@iamvictor
Hidden Gem
@greg319
Fantastic tool for working with clients
@devdbydesign
An Essential Tool for Enhancing Communication with Clients
@Fiorenzomi
Great product!
@gramir
Very useful product and excellent support
@Ulrich86098
Simple Commenter has changed the way I work
@Jim Langman
Deserves +1000 tacos
@IgnacioJadue
Clients LOVED using Simple Commenter
@Katelyn
Phantastic
@user6961b
They fixed my issue in literal seconds from emailing them
@100587018771155070259
Super handy tool. The developer is very responsive.
@neposeda
I didn't realize how much I needed this tool!
@koen.kerkvliet
Life changed in under 5 minutes
@Dsouldiva
My clients have been engaged like never before
@Jim Langman
Simple. Effective. Game Changer
@Dsouldiva
Finally, a feedback tool my clients actually enjoy
@craigfenton
A Game-Changer for Web Feedback – Worth Every Penny!
@ryanbarilla
The tool I've been searching for
@alexs89
Simple, yet ingenious
@koen.kerkvliet
Great feedback app and so easy to use!
@iamvictor
Hidden Gem
@greg319
Fantastic tool for working with clients
@devdbydesign
An Essential Tool for Enhancing Communication with Clients
@Fiorenzomi
Great product!
@gramir
Very useful product and excellent support
@Ulrich86098
Simple Commenter has changed the way I work
@Jim Langman
Deserves +1000 tacos
@IgnacioJadue
Clients LOVED using Simple Commenter
@Katelyn
Phantastic
@user6961b
They fixed my issue in literal seconds from emailing them
@100587018771155070259
Super handy tool. The developer is very responsive.
@neposeda
I didn't realize how much I needed this tool!
@koen.kerkvliet
Life changed in under 5 minutes
@Dsouldiva
My clients have been engaged like never before
@Jim Langman
FAQ
Questions people ask before they try it
Something missing? Email info@simplecommenter.com and you’ll get an answer from the person who built it.
- What is a bug report?
- A bug report records unexpected software behavior so a team can investigate it. It describes the affected feature and environment, the actions that led to the problem, expected and actual results, and supporting evidence. A useful report distinguishes what was observed from a possible explanation.
- How do I write a good bug report?
- Write a specific title, record the page and environment, and list the steps in order. Separate expected behavior from the result you observed. Add the reproduction frequency, relevant evidence, impact, severity, and proposed priority. Use one report per issue and let the investigating team confirm the cause.
- What does steps to reproduce mean?
- Steps to reproduce are the ordered actions another person follows to try to observe the same bug. Start with the required login state or setup, name the controls and test data, and end at the point where the unexpected behavior appears. Record intermittent failures honestly, such as two failures in five attempts.
- How is a bug report different from a bug tracking template?
- A bug report contains the details of one issue. A bug tracking template summarizes many issues, usually with an ID, title, owner, status, severity, and priority. Use the tracking table on this page as an index and link each row to its full report so reproduction steps and evidence stay available.
- Can I use this bug ticket template in Word, Google Docs, or Jira?
- Yes. Download the .docx for Word or import it into Google Docs. Copy the Markdown into a supported editor or paste the fields into your issue tracker, adjusting formatting as needed. This issue report template is independent of a particular tracker and can be adapted for websites, applications, or internal tools.
- What if I cannot reproduce the bug again?
- Report what you observed and say that you have not reproduced it again. Keep the time, environment, last actions, and available screenshot or error details. Include your later attempts and their outcomes. An intermittent bug report is useful without claiming that the problem happens every time.
- Is this bug reporting template free?
- Yes. Fill in the form, copy the report as Markdown, or download a Word .docx without an email address or account. The completed website bug report example is also free to read and adapt. You can use the template with any bug reporting system.
- Can Simple Commenter fill in every field automatically?
- Simple Commenter can capture page and browser context, screenshots when enabled, and available JavaScript errors with website feedback. An available AI developer brief can help describe the issue for your team or a connected MCP agent. You still provide the actions you took, expected behavior, and business impact; the captured context does not prove a root cause or a correct fix.
Keep the report with the page it describes
Use the free template for your next issue. When your team is reviewing a website, Simple Commenter lets them pin feedback to the page and keep captured context, replies, and progress together.
No credit card required.
Plan the test with the website QA checklist, review client changes with the staging site review checklist, or explore the website feedback tool.