Organize your backlog and map child work items to parents in Azure Boards
TFS 2017 | TFS 2015 | TFS 2013
After you've added features or epics to your portfolio backlog, organize your backlog by mapping backlog items. You can quickly add and group items into a hierarchy. And also drill up or down within the hierarchy, reorder and reparent items, and filter hierarchical views.
In this article you'll learn how to:
- Open your product backlog or portfolio backlog
- View the tree hierarchy
- Group backlog items using the Mapping pane
- Reparent items using drag-and-drop
Note
To understand the differences between backlogs, boards, and taskboards, see Backlogs, and boards. If your backlog or board doesn't show the work items that you expect or want, see Set up your backlogs and boards.
Prerequisites
Backlogs are automatically created when you create a project or add a team. Each team has access to their own product, portfolio, and sprint backlogs as described in About teams and Agile tools.
- You must connect to a project. If you don't have a project yet, create one.
- You must be added to a project as a member of the Contributors or Project Administrators security group. To get added, Add users to a project or team.
- To add or modify work items, you must be granted Stakeholder access or higher. For details, see Stakeholder access quick reference.
- To view or modify work items, you must have your View work items in this node and Edit work items in this node permissions set to Allow. By default, the Contributors group has this permission set. To learn more, see Set permissions and access for work tracking.
Stakeholder access users can't use drag and drop to map or reparent work items or change their sprint.
Open your backlog from the web portal
From your web browser, open your product backlog.
From your web browser, open your team's product backlog. Select Boards>Backlogs.
Note
The images you see from your web portal may differ from the images you see in this article. These differences result from updates made to your web app, options that you or your admin have enabled, and which process was chosen when creating your project—Agile, Basic, Scrum, or CMMI. The Basic process is available with Azure DevOps Server 2019 Update 1 and later versions.
Show parent tasks and expand the tree hierarchy
From the product backlog page, set Parents to Show when you want to drill up or down within the hierarchy. You can also drag and drop items to reparent items from this view.
Use the expand 
and collapse 
icons to expand or collapse one level of the hierarchy.
Map items to group them under a feature or epic
If you've already created your backlog, and now you want to organize it, you can do that most easily by mapping child items to parents.
To map a backlog item under a feature, you first turn on mapping from your backlog (Backlog items, Stories, or Requirements). Next, find the Unparented backlog items group by turning the Parents control to Show. Unparented backlog items will appear at the end of the parented set of backlog items.
Drag items that are currently unparented to the feature under which they belong. Also, you can drag a backlog item to a different feature to change its parent. This mapping creates parent-child links from feature to user stories, which is captured in the 
(links) tab.
To multi-select work items on the backlog and sprint backlogs, it requires TFS 2015.1 or later versions. This feature works in the same way as multi-select works within query results.
It's the same process to map features to epics. From the Features backlog, drag features to an epic listed under the mapping pane.
Change the parent task and reorder items
When you need to change the order or grouping, drag the item to its new location.
You can reparent an item using the mapping pane, or drag it within the hierarchy to change its parent.
You can only reparent backlog items under other features, and features under other epics.
Also, to change an item's priority within a group, drag the item up or down within its hierarchical group. Reordering from a portfolio backlog works the same as when you moved items into priority order on your product backlog.
Limitations on reordering backlog items owned by other teams
If you find you can't reorder a backlog item, check whether the 
info icon appears in the first column as shown in the following image.
You can reparent items owned by other teams, but you can't reorder items owned by other teams. For more information, see Backlogs, portfolios, and Agile project management, Work with multi-team ownership of backlog items.
Add portfolio backlog levels and boards
If you need more than two portfolio backlogs, you can add up to two more for a total of five backlog levels.
You can add them by defining additional work item types and then customizing your process configuration. You can also add or modify the fields defined for a work item type (WIT) or add a custom WIT. To learn more, see Customize the On-premises XML process model and Add a portfolio backlog level.