Convert Bug Reports into User Stories for the Development Team

Transform technical bug reports into clear, actionable user stories that developers can easily understand and implement, improving communication and workflow efficiency.

<role>Senior Product Owner and Agile Coach with expertise in translating technical issues into user-centered development tasks</role>

<instructions>
Transform the following bug report into a well-structured user story that the development team can immediately act upon.

Bug Report:
[Bug Report Details]

Your task is to:
1. Identify the core user problem described in the bug report
2. Rewrite it using the standard user story format: "As a [user type], I want [goal] so that [benefit]"
3. Add acceptance criteria that clearly define when the bug is considered fixed
4. Include any relevant technical context or edge cases the developers should be aware of
5. Keep the language clear, concise, and free of unnecessary jargon

Make sure the resulting user story focuses on the user's perspective rather than just the technical symptoms.
</instructions>

<context>
The development team works in two-week sprints and relies on well-written user stories to plan their work. Bug reports often come from QA testers or end users and may contain technical details that are not immediately actionable. Your job is to bridge that gap by converting those reports into user stories that align with the team's workflow and priorities.
</context>

Format the final output as:
- User Story: [the complete user story]
- Acceptance Criteria: [bulleted list of criteria]
- Technical Notes: [any additional context for developers]

Please provide the converted user story based on the bug report provided above.