A good bug report removes guesswork. It tells engineering what happened, where it happened, who was affected, and how to reproduce the issue without asking the customer three more questions.
For SaaS teams, the best bug reports also connect to support and product context. A broken workflow may affect a single trial user, a high-value customer, or a whole segment. That context changes priority.
Use this template when a bug is confirmed and ready for engineering review. If you want to capture the evidence automatically, start from Gleap’s in-app bug reporting or the website feedback tool.
Copy-and-paste bug report template
Title:
Summary:
Affected user or account:
Environment:
- App/platform:
- Browser/device:
- OS:
- App version/build:
- URL or screen:
Expected behavior:
Actual behavior:
Steps to reproduce:
1.
2.
3.
Evidence:
- Screenshot:
- Session replay:
- Console logs:
- Network request:
Impact:
- How many users are affected?
- Which customer segment or plan?
- Is there revenue, onboarding, data loss, or security impact?
Severity:
Owner:
Related tickets, feedback, or roadmap items:How to fill it out
Title
Write the title as a specific failure, not a vague symptom. “Export button returns 500 for CSV files over 10 MB” is better than “Export broken.”
Summary
Use one or two sentences. A good summary helps a developer decide whether the bug is frontend, backend, integration, permissions, billing, or data related.
Expected and actual behavior
Expected behavior explains what should have happened. Actual behavior explains what the user saw instead. Keep both factual.
Steps to reproduce
Reproduction steps should start from a known state. Include the user’s role, plan, feature flag, data state, or permission level if it matters.
Evidence
Screenshots are useful, but they are rarely enough. The most useful reports include session replay, console logs, network requests, browser or device details, and the affected account.
Impact
Impact separates annoying bugs from business-critical bugs. A bug blocking trial activation should usually outrank a visual issue on a rarely used settings page.
Example bug report
Title:
CSV export fails for workspace admins when filtered table has more than 10,000 rows.
Summary:
Admins can start an export, but the request returns 500 after 8-10 seconds. The issue appears only when the table is filtered by date range.
Affected user or account:
Acme Inc, admin role, Pro plan.
Environment:
Chrome 125, macOS, production app, /reports/activity.
Expected behavior:
The filtered CSV downloads successfully.
Actual behavior:
The export button shows a loading state, then the user sees "Something went wrong."
Steps to reproduce:
1. Log in as a workspace admin.
2. Open Activity Reports.
3. Filter the table to last 90 days.
4. Click Export CSV.
Evidence:
Session replay attached. Network request POST /exports returns 500. Console log shows export job timeout.
Impact:
Three enterprise accounts reported the same issue this week. Blocks compliance reporting.
Severity:
High.Automate the boring parts
Manual templates are useful, but they rely on the reporter knowing what to include. In practice, users forget browser versions, reproduction steps, and network details.
Gleap captures that context automatically: annotated screenshot, session replay, console logs, network requests, device metadata, URL, user profile, and account context. Confirmed bugs can move into Kai Resolve investigation and Kai Code planning so the report becomes implementation work instead of another vague ticket.
Use the template for team discipline. Use bug reporting software to make the evidence automatic.