Key Concepts

Last updated:

Board Studio turns Jira work into a decision view. Start with the outcome you need, then choose the structure, dependencies, and level of detail that make the answer visible.

Start with the decision you need to make

When you need to Use
See the work that matters to a team, release, or programme A Jira Space or saved Filter as the data source
Compare work by schedule, ownership, status, or another Jira field Swimlanes, timelines, and grouping
Understand what is blocked or what could be affected Jira links, dependency roll-ups, and impact analysis
Move from a portfolio outcome to its underlying delivery work Hierarchy levels and semantic zoom
Find risks and understand the evidence behind them Board attention, AI insights, and the Inspector
Keep and share a useful planning perspective A saved board configuration

The same Jira work can support several decisions. You do not need one permanent layout. Save different boards for different planning questions.

Think in five steps

1. Choose the work in scope

A data source defines the Jira work available to the board:

  • Choose a Space for work from one Jira project.
  • Choose a Filter for a saved JQL scope, including cross-project work.

The board can only assess and visualise work available through that scope or retrieved for a supported analysis. Coverage statements in the Inspector identify what was checked.

2. Arrange work to expose a pattern

Use Jira fields as dimensions to answer a comparison question. For example:

  • Put Sprint on a timeline to see when work is planned.
  • Add Project rows to expose cross-project hand-offs.
  • Group by Priority to separate urgent work within each board area.
  • Sort by Status to make delivery progress easier to scan.

Board Studio applies structure in this order:

  1. Swimlanes create the board grid.
  2. Grouping organises cards inside each grid area.
  3. Links connect related work across the resulting view.

Note: Board Studio’s labels describe the dividing lines. Horizontal swimlanes create columns; vertical swimlanes create rows.

3. Add the relationships that explain delivery

Links turn a collection of cards into a delivery network. Enable only the link types and directions that answer the current question.

At a higher hierarchy level, Board Studio can roll several underlying Jira links into one parent-level connection. The rolled-up link preserves the summary while the Inspector lets you examine its constituents.

4. Change detail without losing context

Hierarchy levels let you move between outcomes and delivery detail. Semantic zoom changes which level is shown rather than merely enlarging the same cards.

Use a higher level to understand the portfolio shape. Continue to a lower level when you need the stories, tasks, or dependency evidence behind it. Selection, pins, and Inspector context help you keep your place.

5. Investigate and act

Use Board attention to find unresolved work through deterministic warning signals without invoking AI. Use Selection in the Inspector to understand a chosen card, group of cards, or dependency. When enabled by an administrator, AI insights adds a user-initiated, evidence-grounded risk assessment for a selected work item.

Depending on the available data and enabled capabilities, the Inspector can help you:

  • Trace prerequisites and downstream consequences.
  • Review details, children, relationships, and selected-card summaries.
  • Assess risk with AI insights grounded in Jira evidence.
  • Highlight evidence on the board, locate work, or continue in Jira.

Features and terms

After the outcome and workflow are clear, use this glossary to recognise the controls that implement them.

Term Meaning
Card A Jira work item shown at the active hierarchy level. Its layout can include identity, status, ownership, estimates, configured fields, and roll-ups.
Dimension A Jira field used to arrange, group, or sort cards. Dimensions can use field-aware ordering rather than alphabetical ordering alone.
Swimlane A grid division based on a dimension. Multiple dimensions create nested headers.
Timeline A date-proportional swimlane for fields such as Sprint or Fix Version, including an Unscheduled area when needed.
Group A cluster of cards inside a board area. Groups can be expanded or collapsed; collapsed groups can summarise their links.
Link A visible Jira relationship with independent outward and inward controls, styling, and direction.
Dependency roll-up A parent-level line that represents one or more links between descendants.
Hierarchy level The type of Jira work currently represented as cards, from higher-level outcomes to detailed delivery work.
Selection The cards and links currently chosen for explanation in the Inspector. A selection can contain one item, several items, or work selected through a board header.
Focus mode A temporary view that emphasises selected work and its chosen neighbourhood while preserving the board layout.
Board attention An Inspector view that ranks unresolved work using traceable warning signals in the available board data.
AI insights Optional evidence-grounded risk guidance for a selected work item and the chosen hierarchy coverage.
Pin A card or link kept in the Inspector working set while the selection or hierarchy level changes.
Board configuration A saved combination of data source, structure, sorting, link controls, and display preferences.
Auto update Synchronisation that refreshes the board when relevant Jira work or links change.

Keep Jira as the source of truth

Board Studio reorganises and explains Jira information; it does not create a separate planning dataset. Opening an item in Jira takes you back to the underlying work record. What you see and what an analysis can conclude depend on your Jira access and the data available to the board.

Next steps