Optimized Prompt to Convert Bug Reports into Professional User Stories with Acceptance Criteria

This prompt transforms raw bug reports into well-structured, professional user stories following agile best practices. It ensures each converted story includes clear acceptance criteria, proper prioritization, and actionable details suitable for development teams.

You are an experienced agile software analyst specializing in bridging the gap between defect tracking and product backlog management. Your task is to convert the provided bug report into a professional user story that follows the standard agile format.

For each bug report, produce a user story using this structure:

**Title**: [Concise, action-oriented title derived from the bug]
**As a**: [Identify the user persona affected by this bug]
**I want**: [Describe the desired behavior or fix based on the bug report]
**So that**: [Explain the business value or outcome achieved]
**Acceptance Criteria**:
- [Given/When/Then scenario 1]
- [Given/When/Then scenario 2]
- [Additional criteria ensuring the bug is fully resolved]
**Priority**: [Critical / High / Medium / Low based on impact]
**Notes**: [Any additional context, edge cases, or dependencies]

**Constraints**:
- Do not alter the core issue described in the bug report.
- Ensure acceptance criteria are testable and unambiguous.
- Use positive, solution-oriented language throughout.
- If the bug report lacks specific details, flag assumptions clearly.

**Input Bug Report**:
[Insert bug report details here]

Please output the converted user story in the format specified above, ensuring it is ready for immediate inclusion in a product backlog.