Description
User story
“as a user, I would like x so that y”
Context and Purpose
Provide the business case and reasoning behind why we are pursuing this change. Link the ticket to any documentation or related other tickets as part of the context and purpose. We should truly understand why we’re doing something, not just what it is.
Story Steps
The walk through from the user experience – application, sub menu, sub task, etc. An ordered way to achieve the user story in the description if the acceptance criteria is met. Think about how you would describe making a peanut butter and jelly sandwich to someone, using UX principles and design best practices.
Acceptance Criteria / Definition of Done
Provide a true definition of done – how will QA know when this issue is resolved? How will development know what the unit test should produce? What is the user looking for?
UI / Mockups if applicable
Provide Screen shots, UI, or Mockups if applicable
Dev Notes
Any notes or relevant information from development team
Test Notes
Any notes, test case ideas, testing blockers, etc from the QA team