What this screen is for
A user story describes a requirement from the point of view of the person who wants it. This table lists them with the story title and its "as a ..." line, the project, the sprint it is planned into, the story points, the priority, the status, how many tasks hang off it, and the assignee. Filters narrow by project, by sprint and by status.
When to use it
Use it when writing up requirements and when estimating: story points entered here are what the backlog totals and what the velocity report measures. It is also the quickest way to find every story still unassigned to a sprint.
What you see on this screen
- Story — the title, with the as-a line beneath it.
- Project — which project it belongs to.
- Sprint — the sprint it is planned into, or a dash.
- Points — the story point estimate.
- Priority — low, medium, high or urgent.
- Status — where the story has got to.
- Tasks — how many work items hang off it.
- Assignee — who holds it, or a dash.
- Actions — edit and delete.
Clicking a row opens the story.
Filters and actions
The Filters button reveals three lists — project, sprint and status — and a Reset. Filtering sprint to nothing in particular is how you find stories that have not yet been planned into one. New Story creates one.
Status values
Story statuses are set by your company under Status Management; a new story starts at backlog. Priority is fixed at four values: low, medium (the default), high and urgent.
Related
- Backlog — the same stories in priority order with their child items
- Sprints — the cycles stories are planned into