Browse QA Engineers Section 7: Bug Reports & Defect Management

Structured Bug Report from Observation

23 fill-in slots · from The AI Prompt Handbook for QA Engineers

Your details

0/23 filled

Structured Bug Report from Observation

I found a bug. Help me write a clear, complete bug report.

WHAT I OBSERVED:
[Describe what happened in plain language]

WHAT I EXPECTED:
[Describe what should have happened]

DEVICE AND ENVIRONMENT:
- Device: [Model]
- OS: [Version]
- App version: [Version / build number]
- Network: [WiFi / Cellular / Offline]
- Account type: [User role, subscription level]

Write a bug report with:

TITLE: [Concise, searchable — pattern: "[Screen] - [Component] - [Problem]"]

SEVERITY: [P0-Blocker / P1-Critical / P2-Major / P3-Minor / P4-Trivial]
PRIORITY: [Must fix before release / Should fix / Nice to fix / Backlog]

ENVIRONMENT:
- Platform: [iOS / Android]
- Device: [Model]
- OS: [Version]
- App version: [Build]
- Network: [Condition]

REPRODUCTION STEPS:
1. [Precise step]
2. [Precise step]
3. [Precise step]

ACTUAL RESULT: [Exactly what happens]
EXPECTED RESULT: [Exactly what should happen]
FREQUENCY: [Always / Intermittent (~X%) / One-time]

ADDITIONAL CONTEXT:
- Affected platforms: [iOS only / Android only / Both]
- Regression: [Was this working before? Which version?]
- Workaround: [Is there one?]
- Logs/screenshots: [Reference attachments]

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.