huminderhuminder
  • Board Studio
  • Blog
  • Contact
  • Menu Menu

Inspector

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

Use the Inspector to read the Jira details of a selected card or link without leaving the board.

Find the controls

The Inspector and Board insights are neighbours on the canvas toolbar. The numbered circles identify controls, not steps.

Canvas toolbar with numbered circles locating Board insights, Show inspector, enlarged together with neighbouring controls

Find Board insights and the Inspector. The numbers identify controls, not steps.

  • 1. Board insights: open board-wide triage and analysis. Opening it does not run AI.
  • 2. Show inspector: open the rail for the current selection. Select a card or link to inspect its details.

Inspect your first card

Start with one card: select it, choose Show inspector at the right end of the canvas toolbar and open Cards. Check its key, summary and available details. Select a different card to inspect that work instead, then hide the Inspector when finished. No AI assessment or multi-selection is required. The sections below cover wider investigations.

Inspector Cards tab for selected BAC-2 with summary, In Progress status, Story type, actions, Priority and Assignee details

Inspector identifies BAC-2 and shows its available Jira details.

Here, BAC-2 is selected. The Cards tab shows its summary, status, type and available details, with Open in Jira, Locate on board and Copy key actions. You do not need to run AI analysis to read these details.

What you can do with the Inspector

The Inspector is a rail on the right side of the board. Use its Cards and Links tabs to explain the current selection. The Board insights destination opens board-wide triage and analysis without discarding your investigation.

View Use it to
Board insights → Needs attention Find unresolved work with traceable warning signals and follow its causal trail without invoking AI. No selection is required.
Inspector → Cards / Links Inspect the current selection, assess individual risk, analyse impact, and continue in Jira when needed.
Board insights → AI analysis Request an assessment of the loaded source, including work not currently visible on the canvas. See Board insights.

Tip: Expand the Inspector to its full width when you need to read AI guidance, compare several selected items, or review a long dependency path.

Open, widen, or hide the Inspector

To open the Inspector, select Show inspector at the right end of the canvas toolbar, immediately after Board insights, or press Ctrl+I on Windows or Cmd+I on Mac. Board insights is a separate toolbar entry, not a header action.

For an explanation without opening the rail, activate the blue Help button and select the highlighted Inspector control. See Guided Tours and Contextual Help.

When the Inspector is open:

  1. Select the diagonal arrow in the Inspector header to expand the rail to its full width.
  2. Select the opposite diagonal arrow to return to the compact width.
  3. Select ×, or use the keyboard shortcut again, to hide the rail.

Hiding the Inspector does not clear the board selection, pins, or section state. The same sections remain open or closed when you return to that hierarchy level.

Triage the board before selecting work

Open Board insights → Needs attention to start with the work most likely to need a decision. Board Studio ranks unresolved work using warning signals available in the loaded board data. This deterministic triage does not start an AI assessment.

Board insights Needs attention tab listing SEC-7, BAC-25 and OPS-1 with blocker, overdue, ownership and priority warning signals

Needs attention ranks loaded work without starting AI analysis.

This image shows the separate Board insights warning list, not the basic single-card Inspector view described above.

Use the filters to focus the list:

Filter Shows
All Every ranked work item in the current view.
Flagged Work flagged in Jira.
Overdue Work whose due date has passed.
Blocked Work with unresolved incoming blockers.

The ranking can also use supporting evidence such as missing ownership, high priority, and multiple dependencies. Each candidate shows the signals that contributed to its position.

Select Highlight on board to highlight the filtered candidates without changing the selection.

Note: Board attention evaluates the work items and recognised dependencies loaded on the board. The coverage statement at the bottom of the view tells you what was checked. It does not claim that unloaded Jira hierarchy or unavailable dependencies are clear.

Trace why a work item needs attention

Select a candidate in Needs attention to reveal its causal trail. The trail separates prerequisites from downstream work and shows how the paths cross projects.

From the trail, you can:

  • Select Trace on board to highlight prerequisites and downstream items.
  • Select Open inspector to inspect the candidate’s card.
  • Open the lead blocker in Jira.
  • Copy a coordination brief for a status update or hand-off.
  • Select Mark reviewed to create a baseline. The next review identifies added, removed, or updated trail evidence.

Inspect a selected card

Select a card on the board, then open Inspector → Cards. The top of the view keeps the work item identity and immediate actions visible before the analysis sections.

The card view can contain these sections:

Section What it helps you answer
Description What outcome or scope does this work item describe?
Actions Do I need to open Jira, locate the card, or copy its key?
Details Who owns the work, when is it due, and how is it classified or related?
Card layout fields Which configured custom values or child roll-ups also appear on the board card?
AI insights What outcome is at risk, what should happen next, and which Jira evidence supports that guidance?
Upstream impact Which unresolved prerequisites can affect this work item?
Downstream impact Which work items can be affected by this one?
External dependencies Which configured non-blocking prerequisites sit outside a release-like work item?
Child cards Which immediate loaded children can you continue to at their own hierarchy level?

Sections that have no relevant data stay out of the way. AI insights and impact sections can be collapsed independently, and their state is remembered per hierarchy level.

Choose a compact or complete selection view

Collapse analysis sections to scan ownership, dates, classification and relationships. Expand the relevant sections for evidence and impact detail. In a multi-selection, the Selected work items disclosure keeps the list and bulk actions together while leaving Summary and selection-wide impact independent.

Inspector Selected work items list with seven Northstar Epic keys, titles, statuses and bulk Copy keys, Copy JQL and Open all in Jira actions

Seven Epics stay together with Copy keys, Copy JQL and Open all in Jira.

Assess risk with AI insights

Expand AI insights on a selected card, then choose the hierarchy coverage that matches the decision:

Coverage Includes
Board hierarchy The selected work item and descendants available in the loaded board data.
Jira hierarchy The selected work item and accessible descendants retrieved from Jira.
Selected work item only The selected work item without descendants.

Select Assess risk. The assessment can provide:

Subsection What it shows
Hierarchy coverage Whether the assessment uses the selected work item, descendants loaded on the board, or accessible descendants retrieved from Jira.
Outcome at risk The delivery outcome that could be affected and an evidence-grounded explanation of why.
Act now Prioritised recommendations for the people coordinating the work.
Risk factors The Jira evidence that contributes to the Low, Medium, or High assessment.
Caveats Important limitations, uncertainty, and relevant evidence that is unavailable.
Missing data Jira fields whose absence limits the assessment, such as estimates or due dates.

Evidence references provide actions to inspect or locate supporting work and continue to its Jira record. Use Highlight evidence to mark the supporting cards and links, Reveal evidence cards to bring loaded citations into the view, and Frame evidence to move the camera. These actions are independent: revealing cards does not turn on highlights or family corridors.

AI evidence is highlighted in green. This marks the cards and links supporting the finding, not a risk rating or an assurance that the work is healthy. Upstream and downstream impact keep their separate highlighting semantics. Reports show supported content only; a missing section or finding is not evidence that no risk exists.

Multiple findings can stay active together. Collapsing an analysis section or switching between Global and level views does not automatically clear its evidence. A citation may remain unavailable because it is not loaded, or hidden by board settings or a collapsed group. Read the shown/unavailable counts rather than assuming that every citation is visible.

AI insights is advisory. Check the evidence before acting. An assessment is marked as outdated when the underlying evidence or selected hierarchy scope no longer matches it. Select Regenerate when you need a fresh assessment.

Note: AI insights appears only when an administrator has enabled the capability. The Inspector reports disabled, loading, unavailable, and failed states explicitly.

Read a real assessment with its limits

This staging example assesses FRON-42, Approval inbox for pending payments, using Board hierarchy coverage. The selected Story and its three descendants are in scope. The result displays High risk, with one of four evidence items shown and two unavailable in the loaded board data. These visibility limits do not mean the missing items were assessed as safe. Read both the finding and that boundary before deciding what to investigate.

FRON-42 AI insights showing High risk, Board hierarchy scope, an advisory notice and two evidence items unavailable in loaded data

Check the hierarchy scope and unavailable evidence before acting.

The capture was taken after explicitly choosing Analyse; that staging build labels the repeat action Analyse again. Labels may differ from Assess risk or Regenerate in other versions. The assessment is advisory, not a delivery forecast or proof that every cited item is visible on the board. No Jira work was changed by capturing it.

Enable AI insights for your Jira site

A Jira administrator enables AI once for the Board Studio installation. The setting applies to every Board Studio board on that Jira site; it is not configured board by board.

  1. Open Board Studio as a Jira administrator.
  2. Select Settings (the cog icon) in the upper-right corner.
  3. Select the AI tab. This administrator-only tab is not shown to other users.
  4. Turn on AI insights.
  5. Close Settings. The change is saved immediately; there is no separate Save action.

To verify the outcome, select one card, open Inspector → Cards, and expand AI insights. The Assess risk action should be available. Reload Board Studio if it was already open when the setting changed.

Users still choose when to run each assessment, and every assessment respects that user’s Jira permissions. Turning AI insights off again prevents assessments and hides saved AI results across the Jira site; it does not change Jira work.

How AI is governed

Board Studio’s AI insights use Anthropic Claude Haiku 4.5 through Atlassian’s hosted AI service. Board Studio does not call a separate AI endpoint and is classified as Runs on Atlassian. The specific model may change in a later app version as Atlassian’s hosted model availability evolves.

Atlassian’s responsible AI guidance recommends that app documentation identify the model or provider, the customer data processed and its purpose, where people interact with AI, known limitations, and the human controls. Board Studio’s implementation is disclosed below.

Safeguard What it means for you
Model and provider Anthropic Claude Haiku 4.5 is accessed through Atlassian’s hosted AI service.
Administrator control AI is disabled by default and must be enabled by a Jira administrator.
Explicit use Selecting, opening, or navigating the board never starts an assessment. A user must select Assess risk, Regenerate, or the explicit run action in Board insights.
Purpose The model produces an advisory delivery-risk level, outcome, rationale, recommended actions, risk factors, caveats, and evidence references.
Permission-aware input Jira evidence is read with the current user’s permissions. The selected scope can include issue keys, summaries, the selected issue description, issue type, status, priority, assignee display name, update and delivery dates, versions, sprints, estimates, flags, labels, components, hierarchy, and recognised dependencies.
Data minimisation Board Studio includes only the fields needed for the assessment, limits the selected description text and the number of hierarchy and dependency records, and identifies incomplete coverage.
Visible evidence Results show their scope, generation time, risk factors, caveats, and references back to Jira work.
Storage and retention Board Studio stores each user’s generated assessment in Atlassian-hosted app storage for up to 30 days. It does not store the prompt as a separate Board Studio record.
Human accountability Results are advisory. Board Studio does not automatically change Jira work or treat generated guidance as a decision.
Platform safeguards Requests undergo the same Atlassian moderation checks used for Atlassian’s own AI and Rovo features.

Warning: Generated text can be inaccurate, incomplete, or biased. A Low, Medium, or High label is an advisory assessment, not a prediction or Jira status. Verify cited issues, dates, owners, dependencies, and recommendations before acting. Risks outside the selected scope or inaccessible Jira data cannot be assessed.

The experience is designed in line with Atlassian’s AI interaction guidelines: AI stays in the working surface, its state remains visible across navigation, supporting evidence can be inspected, and people retain control of every action. Use the Board Studio Support action to report problematic output.

Analyse prerequisites and consequences

Use the two impact sections to reason in both dependency directions for one selected card or a set of selected cards:

  • Upstream impact follows unresolved blocking paths towards the selected card. Use it to find prerequisites and blockers.
  • Downstream impact follows blocking paths away from the selected card. Use it to understand consequences.

For either direction:

  1. Adjust the depth to control traversal through the loaded hierarchy and recognised Blocks relationships. Hierarchy steps also count towards depth.
  2. Review the count, project breakdown and coverage. For a multi-selection, results distinguish work outside the selected hierarchy from work within it.
  3. Select Highlight impact to add graded highlights without changing the selection. Use Show impact cards separately to reveal the analysis sources and results, including off-level cards.
  4. Select Frame evidence to frame displayed sources, results and displayed family context without revealing more cards or changing the selection.
  5. Select Pin top to keep the highest-impact items available.
  6. Use a row action to locate, pin, or continue to the work item at its board level.

An empty state is still useful evidence. It confirms that no impact was found within the chosen depth and the data available to the board.

Check loaded impact evidence on the board

For FRON-42 in the Frontend staging source, Upstream impact at depth three lists the loaded subtasks FRON-53, FRON-54 and FRON-55. The panel also warns that one referenced item is not loaded. Hierarchy traversal is included, so do not read this list as three direct Jira blocking links.

FRON-42 upstream impact at depth three listing FRON-53, FRON-54 and FRON-55, with Show impact cards and Highlight impact active

Three loaded subtasks are shown; one referenced item is not loaded.

Here, Show impact cards and Highlight impact were activated separately, then Frame evidence brought the displayed evidence into view. The three subtasks appear as context cards with red impact highlights. The warning remains important: revealing loaded cards does not fetch the missing referenced item into this board.

Keep investigations across views

Highlights, card reveals and family corridors are independent. Ending a card reveal keeps cards required by the current view, selection, another investigation or a family reveal. Removing a highlight does not remove its temporary card context.

Changing views preserves investigations and Inspector reading state. Narrowing the selection through Summary pauses the previous impact investigation rather than silently applying it to the new selection. Use Resume on board on a retained investigation when you want its saved highlights and reveals back. The current selection’s impact sections always describe the current selection.

Summarise several selected cards

Select several cards, or select a row, column, sprint, fix version, or unscheduled header. The Cards view becomes a summary of the set.

Expand Summary to break the selection down by the dimensions currently shaping the board. This keeps the explanation aligned with the columns, rows, and timeline you can see.

The example summarises seven selected Northstar Epics by Sprint membership, Project and Priority grouping.

Inspector Summary for seven selected Northstar Epics showing Sprint Columns, Project Rows and Priority grouping distributions

Summary explains Sprint membership, Project Rows and Priority grouping.

  • Discrete dimensions use a distribution bar and ranked values.
  • Timeline dimensions list dated buckets in calendar order and include Unscheduled when needed.
  • A field used on more than one axis is summarised once.
  • Field labels identify their roles in columns, rows or grouping. Coverage distinguishes populated, empty and unavailable values; unavailable is not the same as empty.
  • Expand Other to inspect remaining values. Multi-value fields and spanning timeline cards can contribute to more than one bucket, so bucket counts need not add up to the number of selected cards.
  • Select a value to keep only the matching cards from the current selection and clear selected links. This narrows the selection; it is not a new Jira search.

The Selection section records the board header that produced the set. Expand Selected work items to find the item list and Bulk actions, which let you copy keys, copy JQL, or open the selected work in Jira. Selecting a row exposes that work item’s details without discarding the board selection. The disclosure remembers whether it was open or closed.

Upstream impact, downstream impact and child cards describe the selected set. Individual AI insights require exactly one card selected on the board: choosing an active row in a multi-selection does not turn an individual assessment into an assessment of the whole set. Use Board insights for source-wide AI analysis.

Inspect selected links

Select a direct link or a rolled-up link, then open Inspector → Links.

In this Northstar example, the selected BAC-15 → OPS-6 connection represents three underlying Blocks links. Read the constituent list before deciding which team to contact: BAC-9 blocks OPS-1, while BAC-25 blocks both OPS-1 and OPS-9. Three links involve two distinct sources and two distinct targets, not three blocked Epics.

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.

Use the row’s locate or Jira action to follow the exact work item. This is dependency evidence, not an AI assessment. The enlarged list below shows the three handoffs and their available actions.

Three constituent Blocks links BAC-9 to OPS-1, BAC-25 to OPS-1 and BAC-25 to OPS-9 with hierarchy-level, locate and Jira actions

BAC-9 and BAC-25 connect to OPS-1 and OPS-9.

The Links view explains:

  • The source, target, direction, and number of underlying Jira links.
  • Whether the selected line is direct or aggregated.
  • The hierarchy level being viewed.
  • Constituent links grouped by link type and ordered by risk when risk sorting is active.
  • Source and target statuses.
  • Actions to locate either endpoint, open either issue, copy keys, copy JQL, or open all related work.

When a roll-up contains links from different descendant levels, use the depth filters to focus the evidence. Select Explore handoffs when several constituents need to be opened together at their deepest available level. The Inspector keeps the parent hand-off context visible while you review the underlying links.

Displayed exact endpoints take precedence: their Jira relationship is drawn directly and is not also counted in a residual roll-up. Revealing or collapsing cards can therefore change the split between direct and aggregated lines without changing the underlying Jira relationships. Read the current constituents rather than adding a previous aggregate count to newly visible direct links.

If several links are selected, the summary separates direct and aggregated lines, reports the total underlying dependencies, and counts unique sources and targets. Choose a selected link to review its constituents without losing the rest of the set.

Keep a working set with pins

Pin cards and links that you need to compare or revisit. The pin tray keeps a working set while you move between analysis and selection details.

Pins persist while you change selection or hierarchy level. A pin from another level identifies its home level. Select it to return to that level and locate the item.

Use Highlight pinned to show pinned cards and links on the board without replacing the current selection.

Select work from the board

Action Result
Select a card or link Replace the current selection with that item.
Shift + select Add the item to the selection.
Ctrl/Cmd + select Toggle the item in the selection.
Select empty canvas Clear the selection.
Ctrl/Cmd + select empty canvas Preserve the current selection.
Ctrl/Cmd + A Select every card visible at the current hierarchy level.

Cards and links remain separate inside the Inspector. When both kinds are selected, use the count badges on Cards and Links to move between their explanations.

Undo or redo a selection

Shortcut Action
Ctrl/Cmd + Z Undo the last selection change.
Ctrl/Cmd + Shift + Z or Ctrl/Cmd + Y Redo the selection change.

Selection history is kept per hierarchy level and resets when you change data source.

Related

  • Dependency Roll-ups: reveal and inspect the Jira links represented by a parent-level line.
  • Search: build a precise multi-card selection and continue in the Inspector.
  • Focus Mode: keep selected work and its dependency neighbourhood prominent.
  • Semantic Zoom: move between hierarchy levels while preserving Inspector context and pins.

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

Customize

Essential Functions

Analytics