Team Services | TFS 2017 | TFS 2015 | TFS 2013.4
Feature availability: This feature is available from Team Services and the web portal for TFS 2013.4 and later versions.
As your team identifies code defects or bugs, they can add them to the backlog and track them similar to requirements. Or, they can schedule them to be fixed within a sprint along with other tasks.
When you track bugs as requirements, they'll show up on the product backlog and Kanban board. When you track bugs similar to tasks, they'll show up on the sprint backlogs and task boards.
If you want to track custom WITs on your backlogs or boards, you can.
- For Team Services and the Inheritance process model, see Customize your backlogs or boards for a process.
- For Hosted XML and On-premises XML process models, see Add a work item type to a backlog and board.
For an overview of process models, see Customize your work tracking experience.
Set your team's preferences for tracking bugs
Feature availability: You can manage all your team settings from a common configuration dialog from Team Services or the web portal for TFS 2015 Update 1 or later version.
(Team Services and TFS 2015.1 and later versions) From your team's backlog page, click the (gear icon) to open the common configuration team settings.
(TFS 2015 or TFS 2013.4) Click the , (gear icon) to open the administration page.
From the Overview tab, choose the team whose settings you want to configure, and then click Settings.
Click the Working with bugs tab and choose from the three options available.
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 will be 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 will be associated with the Task category.
Choose the last option if your team manages bugs separate from requirements or tasks. Bugs will be associated with the Bugs category.
Because this setting affects all team members' view of the team backlogs and boards, you must be a team administrator to change the setting. Changing the setting is disabled if you're not a team administrator. Go here to get added as a team administrator.
If, after refreshing a backlog or board, and you don't see bugs where you expect them, review How backlogs and boards display hierarchical (nested) items. Only leaf nodes of nested items will appear on the Kanban or task boards.
Bugs are a common item that teams want to track, and choose how they track it. See Manage bugs for more guidance.
However, what if you want to track other work item types (WITs) on your backlogs and boards?
You can add other WITs—such as change requests, issues, or impediments— by customizing your process or team project, based on the process model you use. For details, see Customize your work tracking experience.
Other quickly configurable options you can make:
- Customize cards on the Kanban board or task board
- Enable backlog levels of interest to your team
- Configure team settings
As indicated in this topic, bugs can appear alongside user stories (requirements or product backlog items) or tasks. You don't need to link bugs to one of these items in order to manage them.
When you manage bugs with requirements or with tasks, they'll show up 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—then not all items may appear on your backlogs and boards. To learn more about how nested items are treated, see Backlogs, boards, and plans-How backlogs and boards display hierarchical (nested) items.
The following error indicates that there is a misconfiguration in either your ProcessConfiguration or Categories definition files.
TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration.
To resolve the error, review the information provided in Add bugs or other work item types to backlogs or boards to make sure that you have configured your XML definition files correctly.