Move between portfolio outcomes and delivery detail with the hierarchy-level picker. Changing hierarchy level changes the work represented on the board; ordinary camera zoom changes its scale.
Find the controls
Use the counted planning-level buttons on the canvas toolbar, not the uncounted configuration tabs in the sidebar. Global combines levels; Story, Epic and other counted buttons choose one main level.
Epic is active. Global, Subtask and Story are neighbouring view choices.
Choose a planning level
The toolbar above the canvas lists detected Jira hierarchy levels with work-item counts, for example Epic (13) or Story (80). Select a counted level button, or use the level dropdown when more levels are available, to navigate to that level.
Try selecting Story when your loaded source contains Stories. Check that Story becomes the active level and inspect a familiar Story card. Then select Epic to compare the parent-level view. This changes the main planning level; the separate Hierarchy menu controls which additional levels are visible, not the camera’s zoom.
Labels follow the Jira issue types configured on the site. Standard levels include Epic, Story/Task/Bug and Subtask. Custom higher levels depend on the site’s Jira hierarchy configuration and plan. The numbers describe loaded work, not every work item in Jira.
Each level can have its own card layout, swimlanes and grouping. Select the level on the canvas before editing its structure in the sidebar. The uncounted sidebar tabs are configuration controls, not a substitute for semantic navigation.
Compare an Epic view with a Story view
These consecutive captures use the same Frontend source from the Northstar Treasury staging example. At Story (10), FRON-42 is selected in a Status column and Priority row. Use this level to inspect delivery work.
FRON-42 is selected in the To Do column and Highest priority row.
Selecting Epic (4) shows four larger pieces of work with configured child counts and story-point totals. FRON-34 is the parent of the selected Story. The Epic cards are different work items, not enlarged Story cards.
The same Frontend source now shows four Epics and their child totals.
The saved configuration uses Status and Priority at Story level and a different arrangement at Epic level. Those are per-level presentation choices, not a universal layout imposed by semantic zoom. Use Navigation History to follow the verified Back action to the selected Story. Camera zoom alone does not change the planning level.
Distinguish level selection from visibility
Epic anchors are shown while Story and Subtask levels remain hidden.
This image illustrates the separate Hierarchy visibility menu and its shown/total counts, not a completed change of active planning level.
Choose between a level and Global view
| View | Use it for |
|---|---|
| Epic, Story, Subtask or a custom level | A planning perspective anchored to one hierarchy level. |
| Global | Loaded work across levels, with expandable families and rolled-up dependencies. |
| Reveal family cards within a level view | Selected cards’ loaded ancestors and children alongside the current planning level. |
See Global view and Family Cards and Hierarchy for mixed-level visibility. A level view can contain temporary off-level context cards, so the active level is not a promise that every visible card has that type.
Read the neighbouring controls
The hierarchy group contains visibility, family corridors, family reveal and Parent Context. Rolled-up links, card content and the date ruler are separate toolbar groups. This organisation does not change semantic navigation or Back/Forward behaviour.
| Control | Purpose |
|---|---|
| Hierarchy | Inspect shown/total counts and show or collapse hierarchy levels. |
| Show family corridors | Explain parent-child paths between already displayed cards. |
| Reveal family cards | Follow the current selection with its loaded ancestors and direct children while enabled. |
| Aggregated child links | Show or hide rolled-up descendant dependency links where available. |
| Parent Context | Follow or pin one parent in the parent legend where available. |
| Edit card content | Configure the card layout for the relevant level. |
| Date ruler | Control the calendar ruler when using a timeline. |
Understand roll-ups
Parent cards can display configured metrics from their children, such as child count, story-point totals, status distribution or completion. Configure those fields in the card layout; they are not a fixed set that every card must display. See Card Roll-ups.
When descendant Jira links are represented at a higher level, Board Studio can combine them into an aggregate dependency line. Select the line to inspect its underlying links, endpoints and available drill actions. Hierarchy corridors and dependency aggregates describe different relationships.
When both exact endpoints are displayed, their relationship is drawn directly and excluded from residual roll-ups. Changing level or revealing cards can change that direct/aggregate split without changing the Jira links.
Keep the investigation while navigating
Changing hierarchy level clears the active Search query. Selection and navigation history are level-aware; Back and Forward let you revisit previous views. Pins, retained impact investigations and AI evidence help you continue the same investigation across level and Global views.
Navigation does not rerun AI. Whole-source Board insights keeps the same analysis scope as you explore its evidence at different levels. A selected-item AI assessment remains tied to its work item and chosen hierarchy coverage.
Camera zoom and timeline cards
Use camera zoom to inspect details or fit a wider area. Timeline cards adapt to the available space, presenting less detail at small scales. A duration bar and its readable content do not have to occupy the same screen width. See Gantt Timeline for date placement and undated work.
Related
- Guided Tours and Contextual Help: use Help on the level picker for an explanation without changing level.



