Show bugs on backlogs and boards

Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013

As your team identifies code defects or bugs, they can add them to the backlog and track them similar to tracking requirements. Or, they can schedule bugs to be fixed within a sprint along with other tasks.

You can define this team setting for the Agile, Scrum, and CMMI processes. The Bug work item type isn't defined for the Basic process, so there isn't a team setting for Basic. Instead, you should track bugs and code defects using the Issue work item type.

When you track bugs as requirements, they appear on the product backlog and Kanban board.

Note

Requirements specify expectations of users for a software product. In Azure Boards, requirements are defined by work items that appear on your product backlog. They correspond to User Stories (Agile), Product Backlog Items (Scrum), Issues (Basic), or Requirements (CMMI) based on the process selected for your project. They also belong to the Requirements Category which manages which work item types appear on the product backlog.

When you track bugs like tasks, the bugs appear on the sprint backlogs and task boards. For more information about other work item types, see Add other work item types to backlogs or boards.

Prerequisites

Set your team's preferences for bug tracking

You can change the setting from a backlog or board view. Here we show how to change it from the board view.

In the Working with bugs dialog, you can select from the following three options.

  • Choose the first option when your team wants to manage bugs similar to requirements. Bugs can be estimated and tracked against team velocity and cumulative flow. Bugs are associated with the Requirements category.

  • Choose the second option when your team wants to manage bugs similar to tasks. Remaining work can be tracked for bugs and tracked against the sprint capacity and burndown. Bugs are associated with the Task category.

  • Choose the last option if your team manages bugs separate from requirements or tasks. Bugs are associated with the Bugs category and won't appear on either backlogs or boards.

  1. Open your Kanban board. If you're not a team admin, get added as one. Only team and project admins can customize the Kanban board.

  2. Choose the gear icon to configure the board and set general team settings.

    Open board settings for a team, vert nav

  3. Choose Working with bugs and then choose the option that best meets your team's way of working.

    Settings, working with bugs dialog

  4. When you're done with your changes, choose Save.

  5. To see the changes, open or refresh the team's backlog or Kanban board.

  1. Open your Kanban board. If you're not a team admin, get added as one. Only team and project admins can customize the Kanban board.

  2. Choose the gear icon to open the settings dialog.

    Open board settings for a team

  3. Choose Working with bugs and then choose the option that best meets your team's way of working.

    Settings, working with bugs dialog

  4. When done with your changes, choose Save.

  5. To see the changes, open or refresh your team's backlog or Kanban board.

Requires TFS 2013.4 or later version.

  1. Open your team settings from the Overview tab of your team's admin context. Your changes are automatically saved.

  2. Choose the gear icon (gear icon) to open the administration page.

    Gear icon provides access to admin pages

  3. From the Overview tab, choose the team whose settings you want to configure, and then choose Settings. Select the option you want. Your changes are automatically saved.

    TFS 2015, web portal, team settings admin page, Working with bugs
  4. To see the changes, open or refresh the team's backlog or Kanban board.

Nested items

Tip

If, after refreshing a backlog or board, you don't see bugs where you expect to see them, review How backlogs and boards display hierarchical (nested) items. Only leaf nodes of nested items appear on the Kanban or task boards.

When you manage bugs with requirements or tasks, they appear on one or more of your Agile tool backlogs and boards. However, if you nest items—create parent-child links of items that belong in either the Requirements or Task categories—not all items may appear on your backlogs and boards. To learn more about how nested items are treated, see How backlogs and boards display hierarchical (nested) items.

Add other work item types to your backlogs or boards

Bugs are a common item that teams want to track, and choose how they track them. For more information, see Manage bugs.

However, what if you want to track other work item types on your backlogs and boards?

You can add other work item types—such as change requests, issues, or impediments—by customizing your process or project, based on the process model you use. For details,

You can add other work item types—such as change requests, issues, or impediments—by customizing your process or project, based on the process model you use. For details, see Add a work item type to a backlog and board.

For an overview of process models, see Customize your work tracking experience.

Create, list, and manage bugs

Bugs that are managed with requirements can be added through the product backlog or Kanban board. When bugs are managed along with tasks, you can add them to a sprint backlog or task board. Or, capture them using other tools. For more information, see Define, triage, and manage bugs.

Tip

Effort should automatically be part of a bug, but if you don't see it, customize the bug work item type for it to appear.

You can review bugs defined for your project by creating a query and specifying the Work Item Type=Bug. Or, open a predefined query, Active Bugs (Agile and CMMI), or Work in Progress (Scrum). For other bug-related tasks, see the following articles: