# Epic AGILE-266 - Present and manage work package dependencies directly on 2D boards

Project: Stream agile
Status: new
URL: https://community.openproject.org/work_packages/AGILE-266

## Detailed specification

### Motivation and background information

**Outcome**

Teams leave a session with a clear, shared understanding of which work packages block or depend on others - and that understanding is encoded in OpenProject, not just visible on a whiteboard that gets discarded. Dependency risks caught during planning are cheaper to resolve than those discovered during execution.

**Why This Matters**

Dependencies between work packages, especially across teams, are one of the leading causes of delivery delay. Today, they are either managed in a separate relationship view, or they are tracked informally in meeting notes and not reflected in the system at all. A planning board that shows work arranged by team and iteration is exactly the right context in which to ask: does this card need something from another team's lane before it can start? Making that question answerable - visually, in the moment - is what this epic is about.

When this epic is complete, a planner reviewing a PI or sprint planning board can see at a glance which cards have which dependencies, draw a new dependency by connecting two cards, and immediately understand whether that dependency crosses a team boundary or an iteration boundary - which are the cases that carry the most risk.

### Acceptance criteria

Builds up on <mention class="mention" data-id="75445" data-type="work_package" data-text="##75445" data-display-id="75445">\#\#75445</mention>

  - Dependency lines between work package cards are visible on the board when dependencies exist, with a clear visual distinction between a dependency.
    
      - Open question: which dependency types do we want to show and how can we allow users to differentiate between them in a visual way?

  - A user can draw a new dependency by connecting two cards on the board, and that relationship is written back to OpenProject without leaving the board.

  - Dependency lines persist as cards are moved.

  - A planner can filter the board to show only cards that have unresolved dependencies, to focus a dependency review conversation.

  - Cards with no dependency issues do not create visual noise; dependency lines are shown on hover or on demand, not permanently cluttered across the board.

### Out of scope

*   presets of whiteboards, e.g. for PI planning, for assigning tasks, for sprint planning, for risk management

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q3 |
| Date |  |
| Votes |  |
| List | RM Jira exit, SAFe |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Rosanna Sibora |
| Feature Lead |  |
| Designer | Julia Racsko |
| Developers | OP Dev Polaris Team |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 40d 0h |

## Description

**As** a facilitator, programme or team coordinator using an interactive whiteboard to organise work across teams and iterations,  
**We want** to see, create, and resolve dependencies between work packages directly on the board,  
**So that** dependency risks are visible in the context where planning decisions are being made, not discovered afterwards in a separate view.
