Ticket properties at a glance
This table summarizes all fields you edit or see in a ticket's detail view. The names match the labels in the app. Which fields appear depends on the ticket type, so the third column shows who each field applies to.
The abbreviations: I Initiative, E Epic, S Story (User Story), D/P Dev and Project Story, W Workitem.
Title and description
| Field | Meaning | Applies to | Effect in views | Details |
|---|---|---|---|---|
| Title | Name of the ticket, editable in place | I, E, S, D/P, W | Shown on every card; you find tickets by title and number in the search | Basic fields |
| Description | Text in the visual or Markdown editor; # links to other tickets | I, E, S, D/P, W | Creates references on the linked tickets | Basic fields |
Sidebar: Status group
| Field | Meaning | Applies to | Effect in views | Details |
|---|---|---|---|---|
| Progress | State of the ticket: Idea, Draft, Ready, Todo, Doing, Done | S, D/P (all six); W (only Todo, Doing, Done); not I and E | Determines the column in the Backlog Kanban and the track and column on the Iteration Board | Basic fields, States |
| Closed | No (open) or Yes (closed), independent of progress | S, D/P; workitems have no Closed | Only user stories that are done and closed count toward velocity; closed stories sit in the Kanban column Closed | Open and closed |
Sidebar: Planning group
| Field | Meaning | Applies to | Effect in views | Details |
|---|---|---|---|---|
| Assignee | Who works on the ticket: Unassigned, Assign to me or a team member | S, D/P, W; not I and E | You can filter by it, for example on the Iteration Board | Basic fields |
| Estimation | Story points on the scale 0, 1, 2, 3, 5, 8, 13, 20, 40, 60, 100 or No estimation | S only | Feeds into sums (Σ), velocity and forecast. Without an estimate of its own, the median counts (≈) | Estimation basics, Estimating in Prepare |
| Rework | Total rework points spent; display only | S only | Filled when a story is closed | Basic fields, Open and closed |
| Release | The story's release or No release | S only | The release is the story's swimlane in the Storyboard and the goal in the Roadmap | Releases |
| Bucket | The bucket in the backlog or No bucket | S, D/P | Determines the row in the Backlog Kanban | Buckets |
Sidebar: Classification group
| Field | Meaning | Applies to | Effect in views | Details |
|---|---|---|---|---|
| Bug | Switch that marks a workitem as a defect | W only | Marker on the card; filter Has Bug | Bugs |
| Color | Card color or None | I, E, S, D/P, W | Band at the top edge of the card | Basic fields, List |
| Tags | Your own labels, picked from the project tags or newly created | I, E, S, D/P, W | Marker on the card; tag filter | Basic fields, Categorization |
Sidebar: Hierarchy group
| Field | Meaning | Applies to | Effect in views | Details |
|---|---|---|---|---|
| Parent | The parent ticket; changing it moves the ticket and can change its type | not I; E, S (changeable); W (display only); D/P have no field | Determines the position in the Storyboard | Hierarchy |
| Convert to | Turns the workitem into a User Story, Dev Story or Project Story | W only | The workitem becomes a standalone story | Hierarchy |
Other areas of the detail view
Outside the sidebar, the detail view also contains the Children section (Hierarchy), References and Dependencies (Dependencies and references), the Lead Times tab (Lead times), the Discussions and Attachments tabs, and the Activity section (Discussions and comments).
No type field, no iteration
The type is shown as text under the title and follows the hierarchy. You don't assign an iteration in the detail view; you plan it on the Iteration Board.