Plan and track work
Azure Boards | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
You track your work by creating work items. This article walks you through creating issues and tasks using a Kanban board for the Basic process, or creating user stories and tasks using for the Agile process.
The Basic process is currently only available from Azure DevOps Services. For on-premises deployments, choose the Agile process.
Choose either the Basic process or Agile process for guidance depending on what process was selected for your project.
The Basic process provides three work item types—epics, issues, and tasks—to plan and track work. We recommend you start by adding issues to track your user stories, bugs, or feature items. If you need to group them into a hierarchy, you can define epics. If you want to track additional details of work, you can add tasks to an issue.
|Work item types||Backlog hierarchy|
Within each work item form, you can describe the work to be done, assign work to project contributors, track status, and collaborate with others through the Discussion section.
Here we show how to add issues and child tasks from the web portal and add details to those work items .
Open the Kanban board
The Issues Kanban board is the best tool for quickly adding issues and child tasks. To open, choose Boards>Boards.
The Epics Kanban board is the best tool for quickly adding epics and issues that are children of those epics. To open the Epics board from the Issues board, choose Epics from the board selector.
Add issues or user stories
From the Issues board, choose New item and start adding those issues you want to track.
Enter return and the system assigns a work item ID to the issue.
To track the work you want to manage, add as many issues that you need.
Add details to an issue or user story
Choose the issue or user story title to open it. Change one or more field values, add a description, or make a note in the Discussion section. You can also choose the Attachments tab and drag-and-drop a file to share the file with others.
For example, here we assign the issue to Raisa Pokrovskaya and we add a discussion note, at-mentioning Raisa.
You can only assign work to a user who has been added to the project.
Choose Save & Close when done.
Enter a description of 255 characters or less. You can always modify the title later.
Assign the work item to the team member responsible for performing the work. Depending on the context you are working in, the drop-down menu will list only team members or contributors to the project.
When the work item is created, the State defaults to the first state in the workflow. As work progresses, update it to reflect the current state.
Use the default first. Update it when you change state as need. Each State is associated with a default reason.
|Area||Choose the area path associated with the product or team, or leave blank until assigned during a planning meeting. To change the dropdown list of areas, see Define area paths and assign to a team.|
|Iteration||Choose the sprint or iteration in which the work is to be completed, or leave it blank and assign it later during a planning meeting. To change the drop-down list of iterations, see Define iteration paths (aka sprints) and configure team iterations.|
|Description||Provide enough detail to create shared understanding of scope and support estimation efforts. Focus on the user, what they want to accomplish, and why. Don't describe how to develop the product. Do provide sufficient details so that your team can write tasks and test cases to implement the item.|
A subjective rating of the issue or task it relates to the business. You can specify the following values:
1: Product cannot ship without the successful resolution of the work item, and it should be addressed as soon as possible.
2: Product cannot ship without the successful resolution of the work item, but it does not need to be addressed immediately.
3: Resolution of the work item is optional based on resources, time, and risk.
4: Resolution of the work item is not required.
Provide a relative estimate of the amount of work required to complete an issue.
Most Agile methods recommend that you set estimates for backlog items based on relative size of work. Such methods include powers of 2 (1, 2, 4, 8) and the Fibonacci sequence (1, 2, 3, 5, 8, etc.). Use any numeric unit of measurement your team prefers.
As work starts, drag the issue from the To Do column to the Doing column. Once completed, move to the Done column.
You can add or rename columns as needed, see Customize your board.
Task checklists provide a quick and easy way to track elements of work which are important to support completing an issue.
To start adding tasks, choose the actions icon for the issue and select the Add Task option.
Enter a title for the task and type Enter when done.
If you have a number of tasks to add, simply keep typing your task titles and type Enter.
You can mark a task as done, expand or collapse the task checklist, or reorder and reparent tasks.
Mark a task as done Reorder and reparent tasks Expand or collapse the checklist To mark a task as complete, check the task checkbox. The task State changes to Done. To reorder a task, drag it within the checklist. To reparent a the task, drag it to another issue on the board. To expand or collapse a task checklist, simply choose the task annotation.
Add details to a task
If you have details you want to add about a task, choose the title, to open it. Change one or more field values, add a description, or make a note in the Discussion section. Choose Save & Close when done.
Here we assign the task to Jamal.
In addition to the fields you can define for an issue, you can specify the following fields for a task to support capacity and time tracking.
The type of activity that is required to perform a task.To learn more about how this field is used, see Capacity planning. Allowed values are:
The amount of work that remains to finish a task. You can specify work in hours or in days. There are no inherent time units associated with this field even though the taskboard always shows "h" for hours in relationship to Remaining Work.
Remaining Work is often used to calculate burn down for a sprint.
Capture comments in the Discussion section
Use the Discussion section within a form to add and review comments about the work under development.
Use the @mention control to notify another team member about the discussion. Simply type @ and their name. Or, bring a group into the discussion by typing @ and the group name, such as a team or security group. To reference another issue, task, or work item, use the #ID control. Type # and a list of work items that you've recently referenced will appear from which you can select.
The rich text editor tool bar displays below the text entry area when you click your cursor within the each text box that can be formatted.
Use the icons— at-mention, #-work-item-ID, and pull-request ID —to facilitate bringing others into the discussion or linking to work items or pull requests. Choose one of these icons and a menu displays with the most recent options that you've previously selected.
Try this next