Card Dependencies — "Red Strings" / PI Program Board

WeKan can visualize card-to-card dependencies as colored, arrow-headed connection lines drawn on top of the board — a SAFe PI-planning style program board ("Red Strings"). This is feature request #3392.

A card can depend on (be connected to) one or more other cards on the same board. Each dependency has a relation type, a color and an icon.

Relation types

The line is always drawn from the right edge of the prerequisite card to the left edge of the dependent card, so direction is visible at a glance. A card with several dependencies draws all of them.

Dependencies never restrict where a card can be moved. You can place a prerequisite card in any list/column (Sprint, week, phase) — WeKan does not enforce "good" dependency ordering.

Web UI

Add / edit / remove dependencies

1. Open a card to its detail view.
2. In the Dependencies section click Add dependency.
3. Choose the relation type and color, then search a card by title and pick it.
4. Each listed dependency shows an icon (colored), the linked card title, a relation-type dropdown, a color picker, an icon picker (pencil) and a remove (×) button. Changes save immediately.

The colored icon + count also appears as a badge on the minicard.

Show the connection lines

In the board header click the Show dependencies toggle (link icon). An SVG overlay draws each dependency as a colored curve following the cards as you scroll/resize. By default the overlay is non-interactive, so cards stay clickable. The toggle (showDependencies) is saved on the board.

Drawing links by dragging

For a piplanning.io / Kendis / Miro-style experience, you can draw links directly on the board — no mode to toggle, cards stay clickable. When the dependency overlay is on (Show dependencies) and you can edit the board, each minicard shows a small connect handle (a dot on its right edge) when you hover it:

• Drag the handle from one card onto another card to create a dependency between them (a dashed guide line follows the cursor while dragging). The new link uses the default relation type/color/icon — edit it afterward as below.
• Click a connection line to open a small editor to change its relation type, color and icon, or delete the link.

Everything else on the board keeps working normally while you do this — only the handle starts a drag, and only the lines themselves are clickable; the rest of the overlay is click-through.

Drawing a line from one card to another

Step 1 — Turn the overlay on (board header: Show dependencies),
         then hover a card. A connect handle (o) appears on its right edge.

   +----------------+
   |  PI Alpha      (o)         +----------------+
   |  list: Sprint 1|           |  PI Beta       |
   +----------------+           |  list: Sprint 2|
                                +----------------+

Step 2 — Press on the handle and drag toward the other card.
         A dashed guide line follows the cursor.

   +----------------+
   |  PI Alpha      (o)- - - - - - - - - >+
   +----------------+           +----------------+
                                |  PI Beta       |
                                +----------------+

Step 3 — Release the mouse over the target card.
         A solid, colored, arrow-headed line is created (PI Alpha -> PI Beta).

   +----------------+
   |  PI Alpha      (o)================>+
   +----------------+           +----------------+
                                |  PI Beta       |
                                +----------------+

Changing a line's relation type, color and icon

Step 1 — Click the connection line itself.

   +----------+                 +----------+
   |  PI Alpha|=======*========>|  PI Beta |
   +----------+    (click)      +----------+

Step 2 — The line editor popup opens. Pick a relation type, a color,
         and an icon — each change is saved immediately.

            +-------------------------------+
            |  Edit dependency              |
            |  Relation type: [ blocks   v] |
            |  Color:         [ #2196f3  ]  |
            |  Icon:  (o) [/] [x] [!] [#]   |
            |  --------------------------   |
            |  x  Remove dependency         |
            +-------------------------------+

Step 3 — The line updates on the board: its color, arrow direction
         (from the relation type) and the minicard badge icon all change.

   +----------+                 +----------+
   |  PI Alpha|##(lock)#=======>|  PI Beta |   (blue "blocks" line)
   +----------+                 +----------+

You can also add/edit/remove a dependency from the card detail's Dependencies section (above) — both routes use the same data.

Filter

The board Filter sidebar has a Filter by dependencies section to show only cards that have a dependency of a given relation type.

Import / Export

• Board Settings → Export offers Dependencies / JSON and Dependencies / SVG. The SVG is a standalone diagram and is round-trippable (each line embeds data-from, data-to, data-type, data-color, data-icon, and card numbers/titles).
• All Boards → New → Import → Dependencies (JSON/SVG) imports lines from a JSON or SVG file into a board you select. Cards are matched by _id first, then by card number, then by exact title, so a file exported from a board can be re-applied to a copy or import of it.

Dependencies are also preserved automatically when you copy a board, copy a card within the same board, and when you export/import a whole board as WeKan JSON (target card ids are remapped; dangling ones dropped). Moving a card to another board drops its now cross-board dependencies.

Importing from other trackers

The Dependencies (JSON/SVG) importer accepts more than WeKan's own export. Cards are matched in the target board by _id, then card number, then exact title, so links from other tools resolve as long as the card titles match.

• Jira: when importing a Jira board (All Boards → New → Import → From Jira), issue links (issuelinks) are mapped best-effort — "blocks" link types become blocks / is-blocked-by (by direction), other link types become related-to.

• Miro: the importer best-effort maps Miro REST API data. Export the board's items and connectors from the Miro API (e.g. GET /v2/boards/{id}/items and GET /v2/boards/{id}/connectors) and import a JSON object containing items (or data) and connectors. Each connector's startItem/endItem are resolved to item titles and matched to WeKan cards by title; a connector caption containing "block"/"fix" maps to that relation type.

• Kendis / piplanning.io and others: these are proprietary tools without a documented public dependency file format. Export their links from their own API and convert to the generic JSON shape, which the importer accepts directly:

  jsonCopy

  { "lines": [ { "fromTitle": "Card A", "toTitle": "Card B", "type": "blocks", "color": "#eb144c" } ] }
  

• GitHub / GitLab and others: no standard machine-readable dependency export, so use the generic JSON shape above.

REST API

Base path: /api/boards/:boardId. All endpoints require a bearer token (Authorization: Bearer <token>). A dependency object is { cardId, type, color, icon }.

type is one of related-to, blocks, is-blocked-by, fixes, is-fixed-by. color is any CSS color (e.g. #eb144c). icon is a FontAwesome 4.7 icon name without the fa- prefix (e.g. link).

These operations are also documented in the generated OpenAPI docs (tag Dependencies).

Python CLI (api.py)

python3 api.py listdependencies BOARDID
python3 api.py listcarddependencies BOARDID CARDID
python3 api.py adddependency BOARDID CARDID TARGETCARDID [TYPE] [COLOR] [ICON]
python3 api.py editdependency BOARDID CARDID TARGETCARDID '{"color":"#2196f3"}'
python3 api.py removedependency BOARDID CARDID TARGETCARDID

# Example: card A blocks card B, drawn as a blue line with a lock icon
python3 api.py adddependency BOARDID CARDA CARDB blocks '#2196f3' lock