huminderhuminder
  • Board Studio
  • Blog
  • Contact
  • Menu Menu

Dependency Links

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

Use Board Studio’s Links section for visual dependency management: reveal blockers, control which Jira issue links appear, and make their direction and meaning easy to read. Each link type row combines two actions:

  • Visibility controls define which outward and inward links are displayed.
  • The pencil button opens the editor that defines how the link looks.

For the planning view behind these controls, see how Board Studio builds an interactive Jira dependency graph across projects and hierarchy levels.

Find the controls

Expand Links in the sidebar. Find the relationship row, then use its outward or inward visibility control. Select the pencil only when you want to change how that relationship looks.

Links sidebar showing Blocks, Relates and Duplicate counts with separate outward and inward visibility and pencil style controls

Every link row combines counts, independent visibility directions and a style editor.

Show a first dependency

To show a first blocking dependency:

  1. Load a source containing Jira issues linked with Blocks.
  2. Expand Links in the left sidebar and find the Blocks row.
  3. Use its outward visibility control to show blocks. Inward is blocked by has a separate control; the pencil changes appearance, not visibility.
  4. Select a displayed connection and open Inspector → Links. Read its source, target and direction to identify which work blocks which.

If there is no Blocks relationship in your loaded work, the guide does not require you to create one. Use an existing link type instead or check the source scope. A parent-level connection may summarise links between its children; the later roll-up reference explains how to inspect those underlying links.

Link type rows

The Links section presents every link type as a row. The controls you need to display or style a link are placed directly on that row, so you can identify the link type before changing it.

Row control What it does
First visibility control Show or hide the outward direction
Second visibility control Show or hide the inward direction
Pencil button Open the style editor for that link type
Blocks row with 32 links, outward blocks enabled, inward is blocked by hidden and a pencil style button

Use the visibility symbols for each direction and the pencil for its appearance.

The green check and red cross are buttons, not status labels. Select either one to change that direction independently. Select the pencil button at the right of the same row to edit its visual style.

Style editor

The Style editor lets you configure the visual appearance of every link type in your Jira instance. Board Studio fetches all available link types directly from Jira (via /rest/api/3/issueLinkType), so you can set up your preferred styling before you load a data source. Select the pencil button on the relevant link type row to begin.

What you see

The editor opens for the selected link type with a live board preview containing generic example cards. It uses the same rendering engine as your board, so you can see how the selected routing, line and arrow settings work together. The example text is not taken from your Jira issues.

Settings are organised into Routing, Line and Arrow. On a wide window, all three groups sit beside the preview. In a narrow or short window, select the visible category tabs to switch groups while keeping the preview in view. Editing direction selects Outward or Inward separately from those categories.

Outward vs. Inward directions

Every Jira link type has two directions. Board Studio lets you style each direction independently so you can visually distinguish link semantics at a glance.

Direction Meaning Example (“Blocks”)
Outward This issue acts on another “blocks”
Inward Another issue acts on this one “is blocked by”

Tip: Use a solid line for outward links and a dashed line for inward links to make dependency direction instantly recognisable.

Style properties

Select the pencil button on any link type row to open the Style Editor modal.

Blocks editor showing generic cards crossed by a red Yarn curve, tension 35, direction controls, Routing, Line and Arrow groups, Cancel and Apply

Routing, Line and Arrow stay beside the preview. Yarn is selected at tension 35.

In a smaller window, the same settings are available through three category tabs:

Compact Blocks editor with the live three-card preview above Routing, Line and Arrow tabs, Yarn tension 35 and visible Cancel and Apply actions

In a smaller window, use Routing, Line and Arrow tabs to find every setting.

The following properties are available. Colour is shared by both directions; the other properties can be set independently:

Property Range / Options Description
Thickness 1 to 6 px Line weight. Thicker lines draw attention to critical dependency types.
Line style Solid · Dashed · Dotted Line pattern. Combine with direction to encode outward vs. inward.
Arrow type Triangle · Circle · Circle-filled · Diamond · None Arrowhead shape at the target end of the link.
Arrow size 0.5 to 3.0× (step 0.1) Scale factor for the arrowhead relative to line thickness.
Colour Theme-aware palette Shared by outward and inward links of this type, with colours that adapt to light and dark mode.
Routing style Orthogonal · Octilinear · Curved · Yarn Choose a path around cards or a hanging thread drawn over them.
Tension 0 to 100, default 35 Available for Yarn. Lower values give the thread more slack; higher values pull it taut. At 100 it is straight.

Choose a routing style

Routing changes the path drawn between cards, not the underlying Jira relationship. Choose a symbol in Routing for the selected link type and direction. The preview updates immediately; click Apply to use the result on your board. Hover over a routing symbol for its explanation.

  • Orthogonal uses horizontal and vertical segments joined by right-angle bends. Use it when you want connectors to follow the board’s rows and columns.
  • Octilinear allows diagonal segments at 45° as well as horizontal and vertical segments. Use it when diagonal approaches make the connections easier to follow.
  • Curved uses smooth connectors routed around cards. Use it when you want rounded paths without drawing over card content.
  • Yarn uses hanging curves drawn above cards, without detours around intervening cards. Use it for the familiar appearance of a physical planning wall.

The exact path depends on card positions and the surrounding board. Routing style does not change link visibility, arrow meaning or dependency direction.

From the planning wall to your Jira board

Remember planning a programme with sticky notes on a wall, connecting related work with pieces of yarn? Yarn routing brings that familiar view to your Jira board. Links form hanging curves between cards, passing over other cards rather than bending around them. Adjust Tension to leave more slack or pull the thread taut. Start at the default of 35, or choose 100 for a straight connection. You are looking at the same Jira dependencies in a different way, not creating or changing the relationships themselves.

Yarn attaches to the closest pair of side midpoints chosen from the left, right and bottom of the connected cards. It never attaches at the top. The hanging shape is a visual style, not a gravity simulation. Where a thread crosses a card, clicking selects the card; select an exposed part of the thread to inspect the link.

Compare Yarn and Curved on an iteration board

To recreate a planning-wall view, use Sprint in Columns with timeline mode off, and Project or Team in Rows. Iterations become ordinary column groups rather than positions on a calendar. Choose the dependencies you want to discuss, then compare Yarn with Curved without changing the cards or visible links.

Choose When it suits your board
Yarn You want the look of threads between sticky notes, with connections passing over intervening cards. Use fewer visible link types if threads obscure card content.
Curved You want smooth connections that detour around cards and keep their content clear of the connecting lines.

Both views contain dependencies. This is a comparison of routing styles, not a board with links versus a board without them.

The examples below use the same Northstar Backend board at Story level: Sprint columns with timeline mode off, Team rows, 12 cards and two outward Blocks links. Card positions, zoom, colour, thickness and arrowheads match. Only routing changes. Yarn uses Tension 10 for a looser, more relaxed thread than the default 35. The enlarged Payment Services row shows where the paths pass over cards or detour around them.

Yarn: threads across the planning wall

Northstar Backend Story board with Sprint columns and Team rows, plus a close-up of two red Yarn links sagging over intervening Payment Services cards at tension 10

The same Sprint columns, Team rows and two Blocks links, with more slack at tension 10.

Curved: paths around the same cards

The identical Northstar Backend Story board and close-up with red Blocks links routed around Payment Services cards instead of hanging across them

The same cards and dependencies. Curved routing takes a path around intervening cards.

Compare the three card-avoiding routes

The three examples below use the same Northstar board with Status columns and Project rows, matching card positions and zoom, and family corridors disabled. Each shows only nine outward Blocks links with identical red colour, solid pattern, 5 px thickness and triangle arrowheads. Only the routing style changes. The enlarged detail shows BAC-4 connecting to FRON-6 around the intervening DAT-1 card.

Orthogonal routing

Horizontal and vertical segments form the detour. The renderer smooths the corners, so a rounded elbow does not by itself mean Curved routing is selected.

Orthogonal routing on the same Northstar Status columns and Project rows, showing nine red solid Blocks links with triangle arrows and a detail of the BAC-4 to FRON-6 detour around DAT-1

Only Blocks links are shown. The BAC-4 to FRON-6 path avoids the intervening DAT-1 card.

Octilinear routing

Diagonal transitions join the horizontal and vertical segments. In this board, the differences are short chamfered transitions with smoothing, rather than long diagonal spans.

Octilinear routing on the same Northstar Status columns and Project rows, showing nine red solid Blocks links with triangle arrows and a detail of the BAC-4 to FRON-6 detour around DAT-1

Only Blocks links are shown. The BAC-4 to FRON-6 path avoids the intervening DAT-1 card.

Curved routing

Smooth bends carry the same dependency around the card obstacle. Compare the enlarged path with the two preceding examples, rather than using colour or arrowheads to identify the routing style.

Curved routing on the same Northstar Status columns and Project rows, showing nine red solid Blocks links with triangle arrows and a detail of the BAC-4 to FRON-6 detour around DAT-1

Only Blocks links are shown. The BAC-4 to FRON-6 path avoids the intervening DAT-1 card.

Combine link styles on one board

Mix routing styles when different relationships need different visual treatment. This Northstar Backend example shows 14 Subtasks in Status and Priority columns with Assignee rows. Four existing Jira links use three routing styles together:

Link type Routing Appearance
Blocks Yarn, tension 10 Red solid threads with triangle arrowheads
Relates Orthogonal Green right-angle path with a filled-circle endpoint
Duplicate Octilinear Blue dashed path with diagonal corner segments and a diamond endpoint

All three use 5 px lines and 3× arrow size. These are example settings, not universal meanings for the colours or shapes. Family corridors are hidden, so the connectors represent Jira links.

The dataset contains three link types, so this board combines three routes rather than inventing a fourth relationship. Curved is shown in the comparison above; on a board with four link types, you can assign a different routing style to each one.

Northstar Backend Subtask board with Status and Priority columns and Assignee rows, combining red hanging Blocks links, green right-angle Relates and a blue dashed diagonal-corner Duplicate link

Blocks: red Yarn at tension 10. Relates: green Orthogonal. Duplicate: blue dashed Octilinear.

Editing workflow

  1. Select the pencil button next to the link type you want to edit.
  2. Under Editing direction, choose Outward or Inward. The editor starts with Outward selected.
  3. Choose a routing style, then adjust Line and Arrow. In a smaller window, select each category tab to reveal its settings. Watch the live preview as you edit.
  4. For Yarn, adjust Tension in Routing. Switching to another routing style and back preserves the tension value while you edit.
  5. Leave Apply styles to both directions off to edit the directions separately, or turn it on to apply subsequent property changes to both. Colour always applies to both directions.
  6. Click Apply to update the current board configuration, or Cancel to discard the editor changes. Use the board’s separate Save action if you want to retain changes in a named board.
Action What happens
Apply Updates styles in the current configuration and redraws the board links. It does not save a named board.
Cancel Discards the editor changes and keeps the previously applied style.
Reset to default Restores the default styles for the selected link type in the editor. Choose Apply to use them or Cancel to keep your previous styles.

Note: Board Studio provides sensible default styles out of the box, with solid outward lines and dashed inward lines, standard thickness, and filled arrows. You only need to customise them if you want a different look.

Display controls

The Display controls show link types that have been discovered in the currently loaded issues. Unlike the Style editor, which is available for all Jira link types, these controls only show types that are actually present in your data.

What you see

Each discovered link type appears as a row with visibility toggles, a count badge, and separate outward/inward controls.

Links visibility columns with green outward checks and red inward crosses for Blocks, Relates and Duplicate

Outward links are enabled while inward links remain hidden for the displayed types.

The first direction is outward and the second is inward. A green check means that direction is shown; a red cross means it is hidden. Click either control to change only that direction for that link type. For example, you can show blocks while hiding is blocked by.

Controls

Control Description
Outward toggle Show or hide outward links of this type
Inward toggle Show or hide inward links of this type
Count badge Number of links of this type found in the loaded data
Sort selector Sort the list by Count (highest first) or Name (alphabetical)
Bulk show / hide Toggle all link types on or off at once

Visibility behaviour

When you hide a link type:

  • Edges disappear from the board instantly. No re-layout occurs.
  • Focus mode excludes hidden link types. Navigating dependencies skips them.
  • Card link indicators update to reflect only visible links.

Tip: Hide non-critical link types (e.g., “Relates to”) to reduce visual clutter and focus on blocking dependencies.

Link type reference

Board Studio supports all standard Jira link types. Here are the most common ones:

Jira link type Outward label Inward label
Blocks “blocks” “is blocked by”
Clones “clones” “is cloned by”
Relates “relates to” “relates to”
Duplicate “duplicates” “is duplicated by”
Parent / Child “is parent of” “is child of”

Custom link types created in your Jira instance are supported automatically. They are available to both the Style editor and Display controls.

Advanced edge behaviours

Live edge updates

Style changes are applied to edges immediately without triggering a board re-layout. The rendering engine updates edge visuals in place, preserving the positions of all cards and swimlanes.
When you select Apply, Board Studio updates the current configuration and redraws the affected edges. No page reload or card movement is required.

Routing around cards or over them

Orthogonal, Octilinear and Curved routing take card obstacles into account. Yarn deliberately ignores those obstacles and draws above cards, like thread laid across a planning wall. Paths adapt to the card positions; choose the style that suits the view rather than expecting every route to avoid card content.

Collapsed group edge aggregation

When groups are collapsed on the board, individual edges between group members are replaced by a single aggregated edge between the collapsed groups. The aggregated edge displays a label showing the count of underlying links by type.

Dependency roll-ups

In real-world programmes, the dependencies that matter, such as “this Epic blocks that Epic”, almost never exist as direct Epic-to-Epic links in Jira. They live as Story-to-Story or Sub-task-to-Sub-task links, several levels below where leadership needs to see them. Dependency roll-ups solve that.

When you turn the toggle on, Board Studio synthesises aggregate edges for underlying child links that cannot already be drawn between their exact displayed endpoints. These residual roll-ups use displayed ancestor context and a distinctive triple-line style, with thickness and a numeric count badge that scale with their constituent links. This makes your programme’s dependency hubs visible at a glance.

Direct links first, residual roll-ups second

If both exact endpoints are displayed, Board Studio draws the direct Jira link and excludes that same underlying relationship from roll-ups. Revealing family or evidence cards, expanding a family, or changing level can expose more exact endpoints. The remaining aggregate badge then counts only the relationships still represented by that roll-up, not the original total plus the direct links. Collapsing detail can move those relationships back into aggregate form. Neither operation changes Jira links.

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.

How to turn it on

Step Action
1 Go to the hierarchy level where you want to see aggregate dependencies.
2 Click Show links rolled up from child items in the separate rolled-up-links group on the canvas toolbar.
3 The board re-renders with aggregate edges at the current hierarchy level.

Click the same button again to hide rolled-up links.

This control is separate from hierarchy visibility and family corridors, which explain parent-child relationships rather than Jira dependency links. Card roll-up metrics are configured in the card-content group, not here.

Tip: Roll-ups are particularly powerful at the Epic level. They reveal cross-team dependency hubs that would otherwise require correlating dozens of separate Story-level links.

Anatomy of an aggregate edge

Visual Meaning
Triple-line style Distinguishes a synthetic, rolled-up edge from a direct Jira link.
Thickness Scales with the number of underlying child links.
Numeric count badge Displays the exact number of underlying links (e.g. “7”).
Source / target Displayed representatives of the underlying endpoints, which can include ancestor cards when exact endpoints are not displayed.
Colour and line pattern Inherited from the link-type style. If multiple link types contribute, the dominant type’s style is used.

Drilling into a rolled-up edge

Aggregate edges are clickable. Selecting one opens the Inspector on its Links tab, which explains the dependency end-to-end:

  • A plain-English summary banner at the top.
  • Depth chips to filter constituents by descendant level (e.g. Stories only).
  • A risk-sorted list of the underlying child links with status lozenges, risk badges, and one-click Locate / Open / Copy keys / Copy JQL actions.
  • Pin the edge for later comparison. The Pin Tray holds up to 3 items.
Inspector constituent list with DAT-16 blocking FRON-25 and DAT-18 blocking FRON-26, status badges and View, Locate and Open actions

The expanded Inspector lists both underlying Subtask links with status and Jira actions.

Roll-ups and semantic zoom

Roll-ups are recomputed automatically as you change hierarchy level:

  • At Epic level, an aggregate edge can represent Story- and Sub-task-level links between displayed Epic families, excluding relationships already drawn directly.
  • At Story level, an aggregate edge can represent Sub-task-level links between displayed Story families, again excluding relationships already drawn directly.
  • At Sub-task level, no roll-up is needed. Links are shown as direct edges.

The Inspector’s pinned edges and selection are preserved across zoom changes; the panel re-anchors to the new level instead of disappearing.

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.

Four selected Subtask cards connected by two red Blocks links among other Subtasks and green Relates links

Both constituent Blocks links are selected and fully visible at their source level.

Why it matters

Pain point How roll-ups solve it
Story-level dependencies are invisible at Epic level, so leadership has no way to see cross-team risk in one view One Epic-to-Epic aggregate edge per dependency cluster, thickness and count badge encoding magnitude.
Manually correlating dozens of separate Jira links to assemble a dependency map Roll-ups synthesise the map automatically from the underlying child links.
Finding which underlying stories cause a given inter-Epic dependency takes 5+ clicks across Jira tabs Click the aggregate edge → Inspector explains it with a one-line summary, risk-sorted constituents, and one-click Locate / Open / Copy actions.
Other tools surface dependencies only in tables or Gantts, not on a hierarchy-aware spatial board Roll-ups render as proper edges on your board, integrated with link styling, focus mode, and the Inspector.

Tips and best practices

Tip Details
Encode direction visually Use solid lines for outward and dashed for inward to make dependency flow obvious.
Use colour to categorise Assign distinct colours to “Blocks” vs. “Relates to” so critical dependencies stand out.
Hide noise Turn off “Relates to” or “Clones” in Display to focus on blocking dependencies.
Style before loading data Pre-configure your preferred link styles in the Style editor before selecting a data source.
Choose what the route should do Use Yarn for a planning-wall appearance or Curved for smooth paths around cards. Compare them with the same visible links before choosing.

Related

  • Guided Tours and Contextual Help: use Help on Links or the rolled-up-links control for an explanation without toggling visibility.

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