Bug Report Template: Free Builder and Examples

Copy this blank bug report template

Use one report per reproducible problem. A useful title names the failed action and the condition that triggers it. Keep the observed behavior separate from your explanation of the cause.

Title: [Action] fails when [condition]
Environment: [App version, browser/OS, device, account role]
Preconditions: [Required setup or test data]
Steps to reproduce:
1. [Starting point]
2. [Action]
3. [Action that reveals the issue]
Expected behavior: [What should happen]
Actual behavior: [What you observed; exact error if available]
Frequency: [Every attempt, intermittent, or observed once]
Impact: [Blocked task, affected users, and available workaround]
Evidence: [Sanitized screenshot, recording, or log reference]
Owner and status: [Who investigates and the next action]

Example: a report that an engineer can reproduce

This fictional example describes an export problem in an imaginary app. The browser version and test conditions belong in the report because they help distinguish a reproducible issue from an isolated failure.

Title: CSV export downloads an empty file when a date filter is active
Environment: Test workspace, app v2.4, desktop Chrome [version]
Preconditions: Three test records dated 1–7 October
Steps to reproduce:
1. Open Reports in the test workspace.
2. Set the date filter to 1–7 October; confirm three rows appear.
3. Select Export CSV and open the downloaded file.
Expected: CSV contains a header and the three displayed records.
Actual: File contains only the header. No error appears.
Frequency: Reproduced in three of three attempts.
Impact: Filtered reporting is blocked. Unfiltered export still works.
Evidence: Sanitized recording attached in the internal issue tracker.

How to report a bug in Slack

Put the title, environment, reproduction steps, expected result, actual result, and impact in the first channel message. Keep follow-up discussion in its thread and add a link to the issue record so the investigation has a stable home.

For the example above, start with “CSV export returns only a header with a date filter active,” then paste the remaining fields. Avoid a message such as “exports are broken” that leaves the reviewer to reconstruct the task. Record the person investigating and the next check.

If you want public-safe feedback from Slack to become votable requests, the Feedbackly Slack integration provides a review step before publication. Keep credentials, personal information, and private incident evidence in your internal support or issue system.

For a format you can paste directly into a channel, use the Slack bug report template. Follow the Slack bug triage guide to turn the report into an investigation and a verified resolution.

Check the report before sending it

• Someone else can start from the stated conditions and follow the steps.
• The expected and actual results describe observable behavior.
• The environment and frequency are recorded, even when the cause is unknown.
• Impact explains the blocked task; priority can be decided during triage.
• Evidence is safe for the intended audience, with an owner and next action.

A bug report documents behavior that fails an expectation. A feature request describes a new or improved capability. For the latter, use the feature request template to capture the problem and desired outcome.