# Bug Report > File one report per defect. Provide enough detail for any engineer to reproduce without asking questions. ## Title ## Classification | Field | Value | |-------|-------| | Severity | Critical / High / Medium / Low | | Priority | P1 (Immediate) / P2 (This sprint) / P3 (Backlog) / P4 (Won't fix) | | Component | | | Discovered In | | | Charter / Test ID | | ### Severity Definitions | Severity | Meaning | |----------|---------| | Critical | Data loss, security breach, system down, revenue stoppage | | High | Major feature broken, no workaround, SLA breach | | Medium | Feature impaired but workaround exists | | Low | Cosmetic, minor inconvenience, documentation error | ## Environment | Field | Value | |-------|-------| | OS / Platform | | | Browser / Client | | | Application Version | | | Environment | | | Relevant Config | | ## Reproduction Steps 1. 2. 3. 4. <...add steps as needed> **Reproducibility:** Always / Sometimes (___ in ___ attempts) / Once (not yet reproduced) ## Expected vs Actual | | Description | |---|-------------| | **Expected** | | | **Actual** | | ## Evidence Attach or link: - [ ] Screenshot / screen recording: - [ ] Error message / stack trace: - [ ] Logs: - [ ] Network capture: - [ ] Test output: ``` ``` ## Additional Context ## Escalation | Condition | Action | |-----------|--------| | Severity = Critical | Blocks release; escalate to engineering leadership within 1 hour | | Severity = High + Priority = P1 | Escalate to team lead within 4 hours | | Unreproducible after 3 attempts | Add to investigation backlog with environment capture |