huminderhuminder
  • Board Studio
  • Blog
  • Contact
  • Menu Menu

Key Concepts

Last updated: 15 November 2026
See Board Studio on Atlassian Marketplace

Board Studio shows Jira work as cards you can arrange and inspect. Start with four terms: a data source chooses the work to load, a card represents a Jira work item, board structure arranges the cards, and a dependency link shows a Jira relationship such as one item blocking another.

Try Your First Board before learning every term below. The tables and five-step model are reference for when you want to extend that first view.

Recognise the parts of a board

Start with the Status and Priority example below. Columns run vertically under status headings such as To Do and In Progress. Rows run horizontally beside priority headings such as High. A card sits where its values meet: a High-priority item in progress belongs in the High row and In Progress column.

Board matrix with To Do, In Progress and Done columns crossed by Low, Medium, High and Highest Priority rows

Each cell combines a Status column and a Priority row.

Grouping adds another level of organisation inside a cell. In this close-up, the Marcus Weber group contains BAC-2, BAC-5 and BAC-7. The group heading identifies their shared assignee; it is not another Jira work item. Its chevron collapses or expands the cards.

Expanded Marcus Weber Assignee group containing BAC-2, BAC-5 and BAC-7 with a downward group chevron

Marcus Weber has three cards in this board cell.

These examples show a board arrangement and a group detail. A dependency link has a different job: it connects related work rather than placing cards into a row or group. In the separate link example below, BAC-15 and OPS-6 are connected through three underlying Blocks relationships. The Inspector lists the actual source and target work so you can check the meaning of the line.

Expanded Links Inspector for BAC-15 to OPS-6 showing three underlying Blocks links, two sources, two targets and all constituent actions

BAC-15 blocks OPS-6 through three descendant links.

Rows, columns and groups change the presentation. Jira relationships provide the dependency evidence. Neither a nearby position nor membership of the same group proves that one card blocks another.

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
Follow parent-child relationships across levels on one canvas Global view, family reveals and family corridors
Find risks and understand the evidence behind them Board attention, AI insights, and the Inspector
Assess outcomes and decisions across the loaded source Board insights → AI analysis
Keep and share a useful planning perspective A saved board configuration
Display a saved view on a Jira dashboard A read-only Board Studio board widget

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:

  • Add Status columns to see work by progress.
  • Optionally add Priority rows to compare urgency.
  • Group by Assignee within each board area.
  • Sort by Created ascending to put older work first within a shared position.

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: Use Columns for vertical bands and Rows for horizontal bands. For timelines and the Board, Polar and Hierarchy layout choices, see Board Configuration.

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.

Use Global when you need several loaded levels together. Reveal family cards follows the current selection, adding its loaded ancestors and direct children while enabled. Show family corridors explains parent-child paths between displayed cards without revealing more cards or highlighting impact.

5. Investigate and act

Use Board insights → Needs attention to find unresolved work worth investigating, using rules and Jira data rather than AI. Use Cards and Links in the Inspector to understand a selection. When enabled by an administrator, AI insights assesses one selected work item; Board insights → AI analysis assesses the accessible project/filter source. Visible cards and current selection do not define that whole-source scope.

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 displayed Jira work item. Global view and temporary reveals can show cards from several levels. Its layout can include identity, status, ownership, estimates, 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.
Global view A canvas combining loaded hierarchy levels with controllable expansion and dependencies.
Family corridor A visual parent-child path, separate from a Jira dependency link.
Evidence reveal Temporary visibility for cards required by an investigation, independent of highlighting and family corridors.
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 by dimming or hiding other work. Dim keeps the layout; Hide adjusts it to the remaining work.
Board attention The deterministic Needs attention view in Board insights, ranking unresolved loaded work using traceable signals.
Whole-source AI analysis A requested interpretation of the accessible project/filter source, not just the visible cards.
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.
Dashboard widget A read-only saved-board view with its own level, labels and refresh cadence, using change events with periodic recovery; viewers still need board and Jira access.
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

  • Create your first board to apply this mental model in four steps.
  • Configure the board to shape swimlanes, grouping, and sorting.
  • Configure links to reveal the dependency directions that matter.
  • Use semantic zoom to move between hierarchy levels.
  • Use the Inspector to assess selected work and trace impact.

Board Studio for Jira Cloud®

  • Overview
    • Getting started
      • Installation
      • Your First Board
      • Key Concepts
    • User Guide
      • Global App Interface
      • Data Sources
      • Board Configuration
        • Working with dimensions
        • Rows
        • Columns
        • Grouping
        • Sorting
      • Dependency Links
      • Managing Configurations
      • Jira Dashboard Widget
      • Settings
      • Sharing Configurations
    • Features
      • Jira Dependency Graph
      • Focus Mode
      • Semantic Zoom
      • Gantt Timeline
      • Card Avatars
      • Rollups
      • Business Logic Detection
      • Auto Update
      • Export
      • Localisation & Themes
      • Guided Tours and Contextual Help
      • Inspector
      • Search
      • Navigation History
      • Parent Context
      • Family Cards and Hierarchy
      • Global View
      • Board Insights
    • FAQ
    • Troubleshooting
    • Support
      • Data Security and Privacy Statement
      • Data Processing Agreement
      • Source Code Licence
      • End User Licence Agreement

Company

Human-led delivery for the AI era.
Contact

Product & Docs

Product

  • Board Studio for Jira Cloud
  • Atlassian Marketplace listing
  • Video library

Documentation

  • Documentation overview
  • Getting started
  • User guide
  • Features
  • FAQ
  • Troubleshooting
  • Support

Legal & Trust

  • Privacy Policy
  • Trust Center
  • SLA
© Copyright huminder 2026, all rights reserved.
  • Link to LinkedIn
  • Link to X Link to X Link to X
  • Link to Youtube
Scroll to top Scroll to top Scroll to top