Create an item
Add a story, a bug, a task, a subtask or an epic to an agile board, with its priority and its estimate.
All the work of an agile board is recorded as items. Each item gets a number with the desk's key (for example, APP-000123) and opens on its own An item's page.
Item types
Type | What it's for |
|---|---|
Story | Something the user needs, written from their point of view |
Bug | A product defect. It has its own details: steps, expected and actual result, environment and severity |
Task | Technical work that isn't a story or a defect |
Subtask | A part of a story, a bug or a task. It always has a parent item |
Epic | Groups stories, tasks and bugs on the same large topic. It doesn't go into a sprint |
Before you start
You must be a Lead, Member or QA of the desk. With the Viewer role you don't see the New item button.
For a subtask, have the parent item's number at hand.
Steps
Open the desk from Desks in the side menu.
Go to Backlog (Scrum) or Board (Scrum and Kanban).
Press New item.
Fill in the form:
Type: Story (selected by default), Task, Bug, Epic or Subtask.
Priority: P1 · Critical, P2 · High, P3 · Medium (selected by default), P4 · Low or P5 · Planned.
Title (required, up to 200 characters). For a story, follow the form the field suggests: As a customer I want… so that…
Description (optional): the details, the context or what the team needs to know.
Points or Estimate (hours): the field depends on how your desk estimates. You can leave it empty and estimate later.
Parent (subtasks only): the number of the item the subtask belongs to, for example APP-000123.
If you create the item from the board during a sprint, the Add to checkbox appears with the sprint's name, checked. Uncheck it if the item should stay in the backlog.
Press Create.
A subtask without a parent isn't created: you see the notice A subtask needs its parent item.
What happens next
The notice with the new item's number appears (for example, APP-000124 created).
In a Scrum desk, the item stays in Backlog, at the end of the list, unless you added it to the sprint. If you add it to a sprint, it moves to To do.
In a Kanban desk, the item goes straight into To do on the board.
A subtask always goes in the same sprint as its parent and moves with it.
The points of stories, tasks and bugs add up to a sprint's commitment. Those of epics and subtasks don't, so they aren't counted twice.