Overview
Board Studio turns Jira issue links into an interactive Jira dependency graph with adaptive routing. Visualise dependencies across projects, teams and other work boundaries on one spatial map, so blockers, direction and delivery risk are easier to trace.
Find the controls
Expand Links in the sidebar. Each link type has separate outward and inward visibility controls. Its pencil opens styling, not visibility.
Use the visibility symbols for each direction and the pencil for its appearance.
Use the visibility control for the direction you need, then select a displayed connection and open Inspector → Links. The Links guide illustrates the menus and style editor in detail.
Read your first dependency
Start with one question: which work is waiting on other work? Display the relevant Jira relationships, then inspect a connection to identify its source, target and direction.
The following pair shows the same 13 Northstar Pilot Launch Evidence cards at Story level, arranged in Project rows and Status columns. Card positions, sizes, zoom and camera are identical.
Without links: the board shows how the work is organised.
Northstar Pilot Launch Evidence: thirteen Story cards organised by Project and Status, with links hidden.
With links: six direct links and seven rolled-up connections reveal dependencies between the cards. The rolled-up connections represent eight child links, so their count badges describe underlying links rather than additional cards.
Identical cards and camera reveal six direct links and seven rolled-up connections representing eight child links.
To read your first dependency, load connected Jira work, enable the relevant direction in Links, then select a connection and open Inspector → Links. Read the link type and source/target direction before deciding which work is blocked. Arrow appearance is configurable, so colour or shape alone is not enough.
A numbered parent-level connection can summarise several Jira links between child items. Its count describes underlying links, not extra cards. Inspect the connection to see those links; the advanced examples below explain routing and roll-ups in more detail.
Visualise Dependencies Without Spaghetti
Dense dependency maps can become difficult to read as the number of links grows. Orthogonal, Octilinear and Curved routing find paths around cards. Yarn deliberately draws hanging threads over intervening cards. The resulting paths depend on the chosen style, board structure, card positions and available space.
The layout engine automatically adapts spacing between cards based on edge density, giving edges more room to route where the board is most connected.
This populated Northstar board combines direct links and rolled-up child dependencies across six projects. Red, 5 px Blocks links use orthogonal routing; the green, 3 px dashed Relates link uses curved routing. Numbered connections identify rolled-up dependencies. Family corridors are disabled, so they cannot be mistaken for Jira links.
Red Blocks use orthogonal routing; green dashed Relates uses curved routing. Numbered dashed connections roll up child links.
Start with the direct paths in the first closeup. BAC-10 blocks DAT-4 and FRON-9, while the green FRON-12 → DAT-4 Relates path is distinguishable by its colour, pattern and routing. The locator in the overview shows where this detail sits on the board.
BAC-10 blocks DAT-4 and FRON-9. The green FRON-12 to DAT-4 Relates path uses a different routing and line style.
The second closeup follows a rolled-up connection. BAC-13 → OPS-3 represents two child links, BAC-26 → OPS-8 and BAC-26 → OPS-9. Its path passes to the right and below OPS-5 rather than crossing that card’s body. This illustrates the routing in this board, not a guarantee that every possible layout is free of crossings.
BAC-13 to OPS-3 represents BAC-26 to OPS-8 and OPS-9. Its routed path passes to the right and below the intervening OPS-5 card.
For matched examples of orthogonal, octilinear and curved routing, see the Choose a routing style section of Dependency Links.
Choose fewer link types when a board is too dense to read. Styling can distinguish relationships, but it cannot replace checking their meaning in the Inspector.
Supported Dependency Types
Board Studio supports all Jira link types, including custom ones:
| Link Type | Outward | Inward |
|---|---|---|
| Blocks | blocks | is blocked by |
| Clones | clones | is cloned by |
| Duplicates | duplicates | is duplicated by |
| Relates | relates to | relates to |
| Causes | causes | is caused by |
| Child/Parent | is child of | is parent of |
| Custom types | ✅ Fully supported | ✅ Fully supported |
Any link type that exists in your Jira instance, including those added by apps or custom configurations, is automatically discovered and rendered.
Per-Link-Type Visual Styling
Each link type and each direction (outward / inward) can have its own independent visual style. Configure these properties per link type:
For step-by-step controls, see how to configure Jira dependency links, including visibility, direction, styling, and roll-ups.
| Property | Options |
|---|---|
| Colour | Theme-aware design token palette |
| Thickness | 1-6 px (step 1) |
| Arrow size | 0.5-3.0× (step 0.1) |
| Line style | Solid, dash, dot |
| Arrow type | Triangle, circle, circle-filled, diamond, none |
| Routing style | Orthogonal, octilinear, curved, Yarn |
The example below combines red Yarn Blocks links at tension 10, green Orthogonal Relates links and blue dashed Octilinear Duplicate links. Read the overview first, then compare the paths and endpoints in the enlarged detail. These are chosen styles, not fixed meanings assigned to colours or shapes.
Blocks: red Yarn at tension 10. Relates: green Orthogonal. Duplicate: blue dashed Octilinear.
Focus Mode Integration
Select a card or link, then explicitly select Focus on the canvas toolbar. Selection alone does not enable Focus. In Focus options, choose Hide others or Dim others and a depth from Selection only to three hops. Use one hop to include directly connected work.
This lets you trace a blocker chain across teams. See Focus Mode for full details.
The Estuary Robotics example selects EST-26 and enables Dim others with one hop. EST-10, EST-16, EST-19, EST-25, EST-26 and EST-27 remain prominent; the other 18 cards fade into the background. Card positions and zoom stay unchanged, so you can compare the dependency neighbourhood without losing its place on the board.
Before: selecting EST-26 alone leaves all 24 cards fully visible.
EST-26 is selected. Focus is still off, so all 24 base cards remain fully visible.
After: Focus keeps the selected card and its one-hop neighbourhood prominent while dimming unrelated work.
Dim others and one hop keep six cards bright while 18 unrelated cards remain visible and dimmed.
Collapsed Group Aggregation
When you collapse a group created with Board Structure → Grouping, its individual cards are hidden but their dependencies aren’t lost. Grouping creates collapsible collections of cards; it is distinct from the swimlanes that divide the board into rows and columns. Board Studio aggregates edges by link type and direction between collapsed groups. Labels or numeric badges indicate how many links a connection represents; the presentation depends on whether the underlying links are direct or already rolled up from another hierarchy level.
Expand a group again to inspect its individual cards and connections. Collapsing a group does not create new Jira links.
The Estuary Robotics example groups 24 cards by Components: Autonomy (5), Field operations (7), Product engineering (5) and Research (7). Focus is off in both states.
Expanded: the overview locates the groups, and the closeup shows individual cards and their connections.
Product engineering and Field operations contain five and seven cards, linked in both directions.
The expanded board has 15 Jira links. Collapsing the four groups produces nine external connections representing 13 of those links. Two Blocks links stay entirely inside Research and are no longer drawn between groups.
Collapsed: the large numbers on the groups count cards. The smaller connection labels count links in each direction.
Product engineering blocks Field operations through three links; two Blocks links run in reverse.
Read the directional counts separately:
- Product engineering → Field operations, blocks (3): EST-18 → EST-19, EST-20 → EST-19 and EST-26 → EST-27.
- Field operations → Product engineering, blocks (2): EST-19 → EST-26 and EST-25 → EST-26.
These counts represent links, not cards. The two directions remain separate even though they connect the same groups.
Collapsed connections can render differently from individual links. In this example, Relates links change from green dashed lines to grey solid arrows when folded; use the relationship labels and direction rather than assuming the expanded styling is preserved.
Aggregate Edges at Hierarchy Level
When viewing parent-level cards via semantic zoom, Board Studio generates synthetic aggregate edges built from child-level links between two parents. Use the separate rolled-up-links toolbar group to control them. Structural links (epic-child, subtask) are excluded from aggregation; family corridors belong to the hierarchy group instead.
These aggregate edges use distinctive “triple-line” styling to distinguish them from individual link edges. Count badges identify the number of underlying links; select the connection to inspect their relationship types and constituent work items.
Direct links take precedence when both exact endpoints are displayed. The same Jira relationship is not also included in a residual roll-up. Expanding a family or revealing evidence cards can expose direct endpoints and reduce the remaining aggregate count without changing Jira. See Dependency Links for the direct-first rule.
| View Level | Edge Display |
|---|---|
| Child level (Stories/Tasks) | Individual edges between issues |
| Parent level (Epics) | Triple-line aggregate edges with link counts |
| Collapsed group | Merged connections with labels or count badges |
In this example, the Epic-level BAC-15 → OPS-6 connection summarises three descendant Blocks links. The Inspector identifies two source items and two target items, so the count is a count of links, not of cards.
BAC-15 blocks OPS-6 through three descendant links.
The constituent list explains the aggregate: BAC-9 → OPS-1, BAC-25 → OPS-1 and BAC-25 → OPS-9. Use it to trace an overview dependency back to the work that creates it.
BAC-9 and BAC-25 connect to OPS-1 and OPS-9.
Cross-Project, Cross-Team and Beyond
Dependencies follow Jira links, not just project boundaries. A link can connect work in different projects, different teams within one project, or both. Board Studio renders these connections on the same board so you can trace a hand-off without switching views.
Use Project and Team as board dimensions when those fields describe your organisation. Other available fields, such as Components, Assignee, Status or Fix versions, can expose dependencies across technical areas, owners, workflow stages or releases. Dimensions organise the cards; they do not create or change the underlying Jira links. Components and teams are distinct fields, even when your organisation uses similar names for them.
Here, Project rows and the actual Jira Team field as columns place 13 cards across six projects and seven named teams. Every displayed card has a Team value.
Project rows and the real Jira Team field show thirteen cards across six projects and seven teams. Components are not used as teams.
The closeup traces two different hand-offs:
- Direct: BAC-10, in Backend and Platform Services, blocks MOB-2, in Mobile Experience and Mobile Team.
- Rolled up: BAC-13, in Backend and Payment Services, connects to OPS-3, in Platform & Release and Platform Services. The count of two represents BAC-26 → OPS-8 and BAC-26 → OPS-9.
BAC-10 in Platform Services blocks MOB-2 in Mobile Team. BAC-13 in Payment Services rolls up two child blockers into OPS-3 in Platform Services.
The Overview section in the configuration panel shows Boundary links, counting Jira relationships with an endpoint outside the loaded dataset, whether observed as inward or outward links. This is a count of links, not necessarily distinct external cards, and it does not load those endpoints or establish their status or accessibility.
Note: Load the work items on both sides of a dependency. For cross-project examples, use a saved Jira Filter covering the relevant projects. Organising the board by Team or another field does not automatically load additional work items.
Interactive Edges
Dependency edges are not just visual; they are interactive:
- Click an edge to select it and inspect its details. Select Focus separately when you want to isolate the selection.
- Aggregate edge labels display tooltips on hover (400 ms delay, 8 s duration) showing the rolled-up link details
- Edges participate in layout morphing: when you change the board structure (add a swimlane, reorder dimensions), edges re-route with a smooth animation
Layout Morphing
Structural changes such as adding a dimension, changing grouping or using Focus with Hide others trigger a smooth morphing animation. Focus with Dim others keeps the layout in place. Full layout changes typically animate over 800 ms, while incremental updates (e.g., a single card move) complete in 500 ms. Cards glide to their new positions, and edges re-route along the way.
This animation is not cosmetic. It preserves spatial context: your eye can follow a card as it moves, keeping you oriented even during major layout changes.
Summary
| Capability | Details |
|---|---|
| Edge routing | Orthogonal, octilinear and curved paths around cards; Yarn threads over intervening cards |
| Link types | All Jira types including custom |
| Styling | Per link type + direction: colour, thickness, arrow size, line style, arrow type, routing |
| Focus mode | Highlight selected card or edge’s dependency chain |
| Group aggregation | Collapsed groups retain connections with labels or count badges |
| Hierarchy aggregation | Triple-line edges with link counts, structural links excluded |
| Cross-project, cross-team and beyond | Trace loaded Jira links across Project, Team and other board dimensions; external link count in Overview |
| Interactivity | Click to select; explicitly enable Focus to isolate; aggregate label tooltips on hover |
| Animation | Layout morphing (800 ms full / 500 ms incremental) |
Related
- Guided Tours and Contextual Help: explain dependency and Focus controls without changing the board.














