Item Hierarchy
See work in context in Manage Items by expanding and collapsing the parent-child hierarchy instead of reading a flat list.
On this page
Work in DevStride is a parent-child hierarchy: a deliverable and its tasks, an epic and its stories, an engagement and its milestones. Manage Items can show that structure inline, so you read work in context rather than as a flat list. Turn it on when you want to see what a parent contains or how items ladder up; turn it off when you just want to sort and scan.
Turning the hierarchy on and off#
The hierarchy controls sit at the left of the toolbar. The leftmost is the tree icon:
- Show hierarchy (tooltip when off) — nest children under their parents. The icon turns green.
- Hide hierarchy — flatten the table back to a plain list.
The same toggle is in Options as Show Hierarchy.
While a Group by field is set, the list is grouped and flat, so both controls are unavailable and say why: Set Group by to None to show the hierarchy. Your setting is kept, and the tree comes back when you set Group by to None.
Expanding and collapsing#
On a row — a parent shows a chevron with the child count (Expand (4 items)). Click it to reveal or hide the children, indented by level and marked with colored depth bars. Children load as you expand; a toast reads Expanding items with the number remaining and a Cancel expanding button while they arrive.
From the toolbar — four buttons open and close the tree one level at a time:
| Button | Shortcut |
|---|---|
| Expand row one level | + |
| Collapse row one level | - |
| Expand all one level | Shift + + |
| Collapse all one level | Shift + - |
+ and - work when the Item cell is focused; the Shift shortcuts work wherever your focus is, outside a text field. → also expands the focused row and ← collapses it or jumps to its parent; Ctrl/Cmd + ↑ / ↓ step between siblings and parents. The table remembers which parents you expanded.
Items that appear in more than one place#
With filters on, an item can match both as a top-level row and as a child of another matching row; an item type with several permitted parents can also sit under more than one parent. The selector beside the tree icon (tooltip: How duplicate items are shown when they match both as a root and as a descendant) decides how such rows show:
| Setting | Effect |
|---|---|
| Children (default) | Show it only under its parent. |
| Primary | Show it only as its own top-level row. The parent shows a note that its matching children already appear above. |
| Both | Show it in both places. |
When filters hide part of a tree#
Filters and hierarchy work together. One filter decides which items match; two switches at the bottom right of the Filters panel decide how the matches are drawn:
| Switch | Off (default) | On |
|---|---|---|
| Filter children | Everything beneath a match shows, matching or not. | Only the items beneath a match that pass your filters show. The Item Type filter is left out of this check, because the items beneath a match are other types by nature. |
| Show parents | Each match is a top-level row. | Each match stays in its real place in the tree. A parent that does not match is shown, dimmed and in italics, only to give the match its place. |
Rows beneath a match are never dimmed. With Show parents off, a parent that does not match is not shown at all; turn it on when you need to see where the matching work sits. Full behaviour: Filtering within the hierarchy.
Moving items while others are editing#
Your item-type rules decide which children a parent may contain. When people move items or change types at the same time, DevStride re-checks the parent-child pairing as it saves. If a competing change (such as an administrator removing a pairing) makes the result invalid, the save is refused rather than written; refresh the affected items and retry.
Why it's useful#
- A project manager opens a deliverable and sees its tasks and their status at once.
- A portfolio manager rolls a program up to its top-level items, then expands only the branches worth a closer look.
- A team sees how its items ladder up into the bigger picture.
Hierarchy is not the same as dependencies
Hierarchy is containment (what is part of what). Dependencies are blocks / blocked by relationships between items. To explore those, see the Dependency Graph; to have dependent dates move automatically, see Link Mode.
The same hierarchy elsewhere
The parent-child display is also available in My Work and in the Table view on boards. For the full Items Table reference, see The Items Table.
Related: Overview · Finding & Filtering Items