Overview
Revisit a previous planning level and its available working context without reconstructing the view.
Find the controls
Use the Back and Forward arrows at the start of the canvas toolbar. These belong to Board Studio, not Chrome.
Back and Forward sit beside the semantic-level controls.
Revisit a view
Use the in-app Back and Forward buttons on the canvas toolbar to revisit hierarchy levels during the current session. Try selecting Story, then Epic, then Back to return to the Story view. These are Board Studio controls, not the browser’s Back and Forward buttons.
The documented navigation history is session-only and starts fresh when Board Studio reloads. Per-level working state is a separate concept; it does not preserve the sequence of visits.
Visit snapshots can include the level and working context:
- The cards and links you had selected
- Where you were panned and zoomed
- Whether Focus Mode was engaged (and at which depth)
- Which inspector items were pinned
Back or Forward rebuilds the destination view and restores available context. Changes to the source, Jira data or available items can limit what can be restored; do not treat history as an exact backup of a previous board.
Follow one Story to Epic and back
These consecutive captures use Lea’s saved Frontend Kanban example on the staging site. The source contains ten Stories arranged by Status and Priority, plus four Epics.
- At Story (10), select FRON-42, Approval inbox for pending payments. Notice its position in To Do and Highest priority.
FRON-42 is selected in the To Do column and Highest priority row.
- Select Epic (4). The same source now shows its four parent-level cards, including FRON-34, Treasury dashboard & payment workbench. This is a level change, not camera enlargement.
The same Frontend source now shows four Epics and their child totals.
- Select the app’s Back button. Check that Story (10) is active again and FRON-42 is selected in the same cell.
Back restored FRON-42, the Story view, its pan position and zoom.
In this replay, the selection, displayed Story keys, pan position and zoom all matched the starting view. Forward is now available. This example verifies one session’s return; it does not promise recovery after a reload or after the source data changes.
How to Use
The two arrow buttons form the navigation-history group on the canvas toolbar. They remain separate from semantic level selection, hierarchy visibility and presentation controls; their navigation behaviour is unchanged.
| Button | Action |
|---|---|
| ← Back | Return to the previous semantic level you visited |
| → Forward | Replay a level you Back’d away from |
Buttons are disabled when there’s nothing to navigate to and while a level rebuild is in progress. Wait for the view to finish changing before navigating again.
What Counts as a “Visit”
A new history entry is recorded whenever you move between hierarchy levels, regardless of how the navigation was triggered.
| Trigger | Recorded as |
|---|---|
| Drilling into an aggregated link | Drill-down |
| Picking a level from the Level Picker | Level picker |
Selection, panning and zooming inside the same level do not create a new history entry. Loading a configuration can initialise the current visit; do not use Back as an undo action for configuration changes.
Note: History is per session. Each time Board Studio reloads, the back/forward stacks start fresh.
What Gets Restored
When you press Back or Forward, the destination’s visit snapshot supplies the context to restore, where still available:
- Viewport: the recorded pan and zoom position
- Selection: previously selected cards and links that remain available
- Focus Mode: the recorded Focus context and depth
- Inspector pins: the available pinned cards and links for that level
If Jira data has changed since your visit, for example an issue was deleted, a link removed or its parent changed, missing items cannot be restored. Check the resulting view rather than assuming an unchanged selection or layout.
Forward Navigation and Focus Mode
Going Back uses the recorded Focus context, subject to the work still available at the destination.
Going Forward through a fresh navigation (not via the Forward button) auto-disengages Focus Mode. This is intentional: when you drill into a new level, you almost always want the full board first, then re-focus from there if needed.
| Action | Focus Mode behaviour |
|---|---|
| Click Back | Uses the destination visit’s recorded Focus context where available |
| Click Forward | Uses the destination visit’s recorded Focus context where available |
| Drill-down or level-picker (fresh navigation) | Auto-disengaged; start fresh on the new level |
Tip: Try Focus on a few cards, visit another level, then select Back. Check the restored selection and Focus depth before continuing the investigation.
Persistence
The history sequence is session-only: reloading Board Studio resets the Back/Forward stacks. Per-level state means the working context associated with an individual level, not a durable list of visits. Do not rely on navigation history to recover a previous session or an exact earlier board state.
Use saved configurations to keep reusable source and presentation choices. Saving a configuration is different from recording a navigation visit.
Common Workflows
Quick Comparison Across Levels
- On a Story-level board, select a few related stories
- Drill up to their parent Epic to see how they roll up
- Click Back to revisit the Story view and check the available restored selection
Recover from a Wrong Drill
Accidentally drilled into the wrong aggregate link? Click Back to revisit the previous level. Check the available selection and context when it returns.
Focused Exploration
Engage Focus Mode on a critical card and its blockers. Visit the parent Initiative level for broader context, then click Back. Review the restored Focus context against the currently available work.
Limitations
- Browser Back / Forward buttons do not control Board Studio. The app runs inside an iframe and uses its own in-app history.
- Keyboard shortcuts for Back / Forward are not available in this release. Use the toolbar buttons.
- History does not survive a page reload; see Persistence above.
Related Features
- Focus Mode: filter the board to a focused subset of cards.
- Semantic Zoom: navigate the Jira hierarchy by changing planning level.
- Inspector: pin cards and links across navigation.
- Guided Tours and Contextual Help: explain Back and Forward without leaving the current view.



