FeedbackFeedback

Bug Report Template

A structured bug report form that guides users through providing the information engineering teams need to diagnose and fix issues. It auto-captures technical context and uses progressive questions to gather reproduction steps without requiring technical expertise from the reporter.

When to Use This Template

Show this template when a user selects "Report a Bug" from the feedback widget, help menu, or error page. It can also be triggered automatically when the app detects an uncaught error or unexpected behavior.

Template Breakdown

1

Describe what happened

Ask the user to describe what went wrong in their own words with a simple text field. Prompt with "What happened?" rather than technical jargon like "Describe the defect."

2

Describe what was expected

Ask "What did you expect to happen instead?" to help the engineering team understand the user's mental model and confirm whether the behavior is truly a bug or a misunderstanding.

3

Capture reproduction steps

Present a numbered list builder where the user can add sequential steps they took before encountering the bug. Pre-fill the first step with their current page URL.

4

Auto-collect environment data

Automatically capture and display the browser name and version, operating system, screen resolution, current URL, and timestamp. Show this to the user for transparency and allow them to add additional context.

5

Attach evidence

Offer buttons to attach a screenshot, screen recording, or file. Include the in-app screenshot tool that captures and annotates the current view with one click.

6

Set severity and submit

Ask the user to indicate the impact: "Blocks my work," "Annoying but I can work around it," or "Minor visual issue." Submit the report and provide a tracking reference number.

Best Practices

  • Pre-fill as much technical context as possible automatically โ€” users should not need to find their browser version manually.
  • Send the reporter a notification when the bug is fixed so they feel their report made a difference.
  • Deduplicate bug reports by checking if a similar report already exists and offering to upvote it instead.
  • Set SLA expectations in the confirmation message โ€” e.g., "Critical bugs are reviewed within 4 hours."
  • Include a link to the status page so users can check if the issue is already known and being worked on.

Use This Template

Sign up for Produktly and use this template to get started in minutes.

Start free trial

Related Templates