Work items

Work is nested so a large outcome stays attached to the tasks that deliver it.

• Epic. Created by a Product Owner. An epic has no parent.
• User Story. Created by a Product Owner. It can stand alone or sit under an epic.
• Feature, Task, and Bug. Created by a Scrum Master or developer, under a user story. Bug is the label for an issue.

Each item gets a stable key such as WEB-14. The key does not change when the title changes.

• Title and a description longer than a few words.
• Acceptance criteria on user stories. The Product Owner owns these statements.
• Story points on user stories. Hover the info icon beside the field for the scale. Points are optional when the story enters a sprint, and they are needed before the story moves to In progress.
• An optional hours estimate on tasks. Hours feed the timer and workload. They are separate from story points.
• An optional subcategory on a bug, task, or feature. Bugs start with Regression, UI/UX, Copy, and Data. Tasks start with Implementation, Research, and Content. Features start with Enhancement and Integration. The Product Owner or Scrum Master can rename, add, or archive options for that project. Archiving keeps the name on items that already use it.
• Assignees. Open estimates split evenly when several people are assigned.

A story point says how big a User Story is compared with the team's other stories. It is not a number of hours or days.

1 is tiny. 3 is small. 5 is a normal story. 8 is large. 13 and 21 are very large, and the team usually splits them.

The Scrum team chooses the number together. The Product Owner does not set or change it.

A story can join a sprint before it has points. Moving it to In progress needs points, a clear description, and acceptance criteria.

Hours are a separate field. Hours record time spent.

• Comments support @ mentions of active project members and optional JPEG, PNG, or WebP images. The toolbar adds bold, italic, code, lists, and an http or https link. The link text is the address. A reply stays on the original comment, one level deep, names the person in that thread you answered, and has no image upload.
• Start timer records time against the item. Stop it from the item or from the header chip.
• Archive hides an item from the active backlog. The key and history remain.