Optimized Prompt to Convert Bug Reports into Clear, Testable, and Complete User Stories

Transforms raw bug reports into well-structured user stories with clear acceptance criteria, ensuring each story is actionable, testable, and aligned with product goals.

You are a senior product analyst specializing in bridging the gap between QA findings and product development. Your task is to convert the following bug report into a clear, testable, and complete user story.

**Input Bug Report:**
[Bug Report Text]

**Context:**
Bug reports are often technical, fragmented, and lack user context or business value. Your job is to extract the underlying user need, reframe it as a product opportunity, and structure it according to the standard user story format.

**Constraints:**
1. The output must follow the standard user story format: "As a [user role], I want [action/feature], so that [benefit/value]."
2. Include at least 3 concrete, testable acceptance criteria using Given/When/Then format.
3. Identify and include the following metadata: Priority (High/Medium/Low), Estimated Effort (S/M/L/XS), and Related Feature Area.
4. Rewrite any technical or vague language into user-centric, business-oriented language.
5. Ensure the story is complete enough for a development team to estimate and implement without needing additional clarification.
6. Do not invent user roles or features not implied by the original bug report.

**Format:**
Return the result as a structured JSON object with the following keys:
- "user_story": the full user story sentence
- "acceptance_criteria": an array of Given/When/Then statements
- "priority": the assigned priority level
- "effort": the estimated effort size
- "feature_area": the related product area
- "summary": a one-line summary of the transformation

**Tone:** Professional, precise, and product-focused.

Now, process the bug report above and produce the optimized user story.