Skip to content

Sample Bug Reports

These examples illustrate how to write clear and actionable bug reports. Each includes the key details an engineer needs to reproduce and diagnose the issue.

1. Navigation Menu Disappears After Login

Environment: - App version: 2.3.1 - Browser: Chrome 113 on Windows 11

Steps to Reproduce: 1. Log in as any user. 2. Wait for the dashboard to load. 3. Attempt to click the navigation menu at the top left.

Expected Result: The menu should remain visible and allow navigation to other pages.

Actual Result: The menu disappears after the page finishes loading, leaving no way to navigate.

Additional Information: A screenshot is attached showing the missing menu. Console logs reveal a JavaScript NullReferenceError in nav.js line 42.

2. Incorrect Sorting in Search Results

Environment: - App version: 2.3.1 - Database: PostgreSQL 14

Steps to Reproduce: 1. Search for "invoice" in the global search bar. 2. Sort the results by date in ascending order.

Expected Result: Results are sorted from oldest to newest by date.

Actual Result: Items appear in random order. The query sent to the server omits the ORDER BY clause.

Additional Information: Occurs for both admin and standard users. The bug appears after the recent search module refactor.

Environment: - App version: 2.3.1 - Device: iPhone 13 running iOS 16.5

Steps to Reproduce: 1. Open the app on a mobile browser. 2. Navigate to the profile page. 3. Scroll to the bottom of the screen.

Expected Result: Profile content should end above the footer with consistent padding.

Actual Result: Text overlaps the footer area, making buttons difficult to tap.

Additional Information: CSS position attributes were recently changed. Reverting commit 1a2b3c locally fixes the issue.