Bug Report

Overview

Generate production-ready bug reports with consistent formatting across your development team, QA workflows, and issue tracking systems like GitHub Issues, Jira, and Linear in under 2 minutes.

Use Cases

• Document browser-specific bugs in Safari, Chrome, Firefox, or Edge with exact version numbers
• Report API endpoint failures during sprint planning and development cycles
• Track mobile app crashes on iOS and Android with device-specific reproduction steps
• Log database query performance issues with execution time metrics
• File UI/UX bugs with accessibility violations and WCAG compliance gaps
• Create security vulnerability reports for penetration testing and code audits

Benefits

Save 5-10 minutes per bug report with pre-structured formatting that includes all details developers need.

Reduce back-and-forth by 60% by capturing environment details, reproduction steps, and expected behavior upfront.

Maintain consistency across 50+ team members using the same report structure for all issues.

Speed up bug triage by 3x when developers can immediately understand severity and impact without follow-up questions.

Improve resolution time by 40% with clear reproduction steps that eliminate guesswork.

Template

Create a bug report:

Bug title: {{title}}
Severity: {{severity}}

Steps to reproduce:
{{steps}}

Expected behavior:
{{expected}}

Actual behavior:
{{actual}}

Environment:
{{environment}}

Additional context: {{context}}

Properties

• title: Single-line Text
• severity: Single Selection Radio (default: Medium)
  • Options: Critical, High, Medium, Low
• steps: Multi-line Text
• expected: Multi-line Text
• actual: Multi-line Text
• environment: Single Selection (default: Production)
  • Options: Production, Staging, Development, Local
• context (optional): Multi-line Text

Example Output

Create a bug report:

Bug title: Login button unresponsive on Safari 17.2
Severity: High

Steps to reproduce:
1. Open app in Safari 17.2 on macOS Sonoma
2. Navigate to /login page
3. Enter valid credentials
4. Click the "Sign In" button

Expected behavior:
User should be authenticated and redirected to dashboard

Actual behavior:
Button shows hover state but click event does not fire. No network requests are sent. Console shows no errors.

Environment:
Production

Additional context: Issue only occurs in Safari. Works correctly in Chrome 120 and Firefox 121. Happens on both desktop and iOS Safari.

Generated response:

Bug Report: Login Button Unresponsive on Safari 17.2

Severity: High

Environment

• Browser: Safari 17.2
• OS: macOS Sonoma
• Environment: Production
• Affected Platforms: Desktop Safari, iOS Safari

Steps to Reproduce

1. Open app in Safari 17.2 on macOS Sonoma
2. Navigate to /login page
3. Enter valid credentials
4. Click the “Sign In” button

Expected Behavior

User should be authenticated and redirected to dashboard upon clicking the Sign In button.

Actual Behavior

• Button displays hover state when cursor moves over it
• Click event does not trigger
• No network requests are sent to authentication endpoint
• Browser console shows no JavaScript errors
• User remains on login page

Browser Compatibility

• Safari 17.2 (Desktop & iOS): Broken
• Chrome 120: Working
• Firefox 121: Working

Suggested Investigation

1. Check for Safari-specific event handling issues with the button click listener
2. Verify z-index stacking - another element may be overlaying the button
3. Review CSS pointer-events property
4. Test with Safari’s Web Inspector to confirm event propagation

Impact

High-severity issue blocking all Safari users from accessing the application, affecting approximately 25-30% of web traffic.

Common Mistakes to Avoid

Vague reproduction steps like “it doesn’t work when I click” make bugs impossible to reproduce. Include the exact sequence of actions, starting from a known state.

Missing environment details force developers to guess which browser version, OS, or deployment environment has the issue. Always specify exact versions.

Confusing symptoms with root causes by writing “the database is broken” when the actual behavior is “query returns 0 results after 30 seconds.” Describe what you observe, not what you think is wrong.

Skipping expected behavior assumes developers know what should happen. State it explicitly so there’s no ambiguity about whether it’s a bug or intended behavior.

Reporting multiple bugs in one ticket makes tracking and resolution harder. File separate reports for the login button issue and the dashboard loading problem.

Forgetting browser-specific context when a bug only appears in Safari or Internet Explorer. Cross-browser testing details help developers prioritize and debug faster.

Using screenshots instead of text for error messages makes them unsearchable. Include the actual text along with screenshots.

Frequently Used With

• Unit Test - Write tests that prevent regression after fixing the bug
• Code Review - Review the fix before merging to production
• Performance Optimization - Document performance-related bugs with metrics

Related Templates

Explore more Coding templates or browse all templates.