ADO Backlog Hierarchy Displays Only Two Levels of the Tree

Question

ADO Backlog Hierarchy Displays Only Two Levels of the Tree

ARCHANA PILLAI 1

Description

In the PME ADO Backlog view, only two levels of the hierarchy can be displayed at a time.

The following message is shown:

“There are too many items on the backlog. Only two levels of the tree can be shown. Delete items or reduce the area of ownership for this team.”

As a result, the complete backlog hierarchy cannot be viewed together. For example, when viewing at the Initiative level, the Initiative and corresponding Epics are visible, but the lower levels of the hierarchy cannot be displayed in the same tree view.

Expected Behavior

The backlog should allow the complete configured hierarchy to be viewed so that the parent-child relationship across backlog levels can be reviewed.

Actual Behavior

Only two levels of the hierarchy are displayed, and ADO shows the message that there are too many items on the backlog.

Rukmini 44,000 Reputation points Microsoft External Staff Moderator

2026-11-11T15:11:28.7566667+00:00
Hello @ARCHANA PILLAI

this message comes from how Azure Boards handles large backlogs, not from a fault in your hierarchy. When a team's backlog contains too many work items, Azure Boards stops expanding the full parent-child tree and shows only two levels at a time, to keep the backlog loading. Azure DevOps also documents a limit of 10,000 work items on a backlog. That number can't be changed, so the fix is to reduce how many items the backlog has to load.

1. Reduce what the backlog includes

In View options, turn off Completed Child Items and In Progress Items if you don't need them in this view. Closed and done children are often the largest share of the tree.

Close or remove work items that are finished or no longer relevant, so they drop out of the backlog.

2. Narrow the team's area of ownership

Under Project settings → Team configuration → Areas, check which area paths the team owns and whether Include sub areas is turned on. If the team owns a broad area tree, the backlog pulls in everything below it.

For very large programmes, split the work across several teams, each owning a smaller area path. Each team's backlog then stays under the limit.

3. View the full hierarchy with a tree query When you need to review parent-child links across every level (for example Initiative → Epic → Feature → Story), a query is better suited than the backlog:

Go to Boards → Queries → New query.

Set Type of query to Tree of work items, with Parent/Child as the link type.

Filter by your area path and iteration as needed, and set the top level to Initiative.

Use Expand all to see every level together.

4. Plan at the higher levels For portfolio-level planning across teams, Delivery Plans show Epics and Features from several team backlogs on a single timeline.

How to check: after reducing the team's scope or turning off completed children, reload the backlog. The message should disappear and the Parents option should expand to every configured level.

If the message still appears after narrowing the scope, please share roughly how many active items the team's backlog contains and which area paths the team owns, and we can look at it further.this message comes from how Azure Boards handles large backlogs, not from a fault in your hierarchy. When a team's backlog contains too many work items, Azure Boards stops expanding the full parent-child tree and shows only two levels at a time, to keep the backlog loading. Azure DevOps also documents a limit of 10,000 work items on a backlog. That number can't be changed, so the fix is to reduce how many items the backlog has to load.

1. Reduce what the backlog includes

In View options, turn off Completed Child Items and In Progress Items if you don't need them in this view. Closed and done children are often the largest share of the tree.

Close or remove work items that are finished or no longer relevant, so they drop out of the backlog.

2. Narrow the team's area of ownership

Under Project settings → Team configuration → Areas, check which area paths the team owns and whether Include sub areas is turned on. If the team owns a broad area tree, the backlog pulls in everything below it.

For very large programmes, split the work across several teams, each owning a smaller area path. Each team's backlog then stays under the limit.

3. View the full hierarchy with a tree query When you need to review parent-child links across every level (for example Initiative → Epic → Feature → Story), a query is better suited than the backlog:

Go to Boards → Queries → New query.

Set Type of query to Tree of work items, with Parent/Child as the link type.

Filter by your area path and iteration as needed, and set the top level to Initiative.

Use Expand all to see every level together.

4. Plan at the higher levels For portfolio-level planning across teams, Delivery Plans show Epics and Features from several team backlogs on a single timeline.

How to check: after reducing the team's scope or turning off completed children, reload the backlog. The message should disappear and the Parents option should expand to every configured level.

If the message still appears after narrowing the scope, please share roughly how many active items the team's backlog contains and which area paths the team owns, and we can look at it further.

1 answer

Your answer

Answer 1

Azure Boards cannot render the complete hierarchy when the team backlog exceeds its display limit; reduce that team’s Area Path scope, or use a Tree of work items query to review the full multi-level hierarchy without relying on the backlog view.

Review the complete hierarchy with a tree query

For the immediate requirement—reviewing Initiative → Epic → lower-level parent-child relationships—create a tree query:

Go to Boards → Queries → All.
Select New → New query.
Change Type of query from Flat list of work items to Tree of work items.
Under the top-level filters, select the Initiative work items you need, for example:
- Team Project = the current project
- Work Item Type = Initiative
- Add an Area Path, state, or other filter to keep the result relevant.
Configure the linked-item criteria for the descendant work items.
Set the link relationship to the parent-child hierarchy and select Match top-level work items first to find linked children.
Run the query and select Expand all.

A Tree of work items query is specifically designed to display multi-tier nested work-item relationships and supports expanding or collapsing the entire returned tree.^1^

To save it under Shared Queries, the user needs at least Basic access and Contribute permission on the destination query folder. A project member can run an existing shared query.

Reduce the backlog scope to restore deeper expansion

The warning indicates that the backlog’s team scope contains too many work items. The applicable display limit depends on the platform:

Azure DevOps Services: 10,000 displayed backlog work items.
Azure DevOps Server / Server 2022: 999 backlog work items.

Items beyond the limit are not deleted; they are hidden from that backlog display. Microsoft recommends adding a team and moving part of the work into the new team’s backlog.^2^

To partition the PME backlog:

Open Project settings → Project configuration → Areas.
Create a child Area Path for a distinct product, business area, active portfolio, or archive scope.
Create or select the team that will own that scope.
Open that team’s configuration and assign the new Area Path to it.
Bulk-update the applicable work items—including their appropriate descendants—to the new Area Path.
Return to Boards → Backlogs for each team and confirm that its backlog is now below the applicable limit.

Area Path assignments determine which work items appear on each team’s backlog. Setting team Area Paths requires Team administrator or Project Administrator permissions; creating or managing project Area Paths generally requires the corresponding node permissions or Project Administrator membership.^3^

Avoid assigning the same Area Path to several teams merely to reproduce the same large backlog. Microsoft documents that overlapping team Area Paths can cause ownership conflicts and unexpected board behavior.

Validate the backlog configuration after reducing scope

Once the team is under the limit:

Open Boards → Backlogs and select Initiatives.
Open View options and turn Parents on.
Enable Completed Child Items if completed descendants must be included.
Clear any active toolbar filter. An active filter normally changes the backlog to a flat list unless Keep hierarchy with filters is enabled.
Use Expand one level repeatedly to expose successive levels.

The backlog view expands or collapses one hierarchy level at a time; its team Area Paths, Iteration Paths, and enabled backlog levels determine what can appear.^4^

If a level remains absent after the item count is reduced, check Project settings → Teams → PME team → Backlogs and ensure each required portfolio or product backlog level is enabled. Active backlog levels control which portfolio, product, and sprint backlogs are available to that team.^5^

Also keep the hierarchy aligned with separate backlog categories—for example, Initiative → Epic → Feature → Story—rather than nesting work items of the same type. Same-category hierarchies are not fully supported by backlog, board, and sprint experiences.^6^

References