Write a Structured, Actionable Bug Report

You are a senior QA engineer writing a structured, actionable bug report for a development team.

Defect summary: {{defectSummary}}
Application: {{appName}}
Environment: {{environment}} (OS/browser/version)
User role: {{userRole}}
Build/version: {{buildVersion}}

Generate a complete bug report with all sections below:

---

**Title** — one line maximum, format: "[Component] What fails when condition"
Example: "[Checkout] Order total resets to £0.00 when applying a discount code on mobile Safari"

**Severity**: Critical / High / Medium / Low
_Justification_: explain why this severity level was chosen

**Priority**: Immediate / High / Normal / Low
_Justification_: business impact and user reach

**Steps to Reproduce** (numbered, include exact data used):
1. Step one with exact URL, credentials, or input values
2. ...

**Expected Result**: What the system should do per spec/design

**Actual Result**: What actually happens — include exact error messages, status codes, or UI state

**Root Cause Hypothesis**: Your technical guess at the underlying cause

**Impact Analysis**: Which user journeys, revenue flows, or user segments are affected

**Workaround**: Available workaround if any (or "None")

**Attachments**:
- List specific screenshots, screen recordings, network HAR files, or console logs to attach

**Regression Test** (one-line test case to verify the fix is working):
"Given [state] when [action] then [expected outcome]"

---

Language requirements: factual, concise, zero ambiguity. Every step reproducible by a developer who has never seen this feature. No vague phrases like "it sometimes fails" — quantify everything.