Relations
Link issues with blocked-by and blocking dependencies.
Relations
Relations express dependencies between issues on the same team (or visible across teams you can read). Pulse supports two symmetric kinds:
| Kind | Meaning |
|---|---|
| Blocked by | This issue cannot finish until the listed issue completes |
| Blocking | This issue prevents the listed issue from finishing |
There is no separate "related" or "duplicate" relation kind in the default UI — use labels or links in description for loose associations.
Add a relation
From issue detail:
- Use Add relation in the sidebar actions (or the relations card header).
- Pick Blocked by or Blocking.
- Search for the target issue by title or ID.
- Save — the relation appears in sidebar cards on both issues.
Remove a relation from the card hover action on either side.
Sidebar cards
Issue detail shows separate Blocked by and Blocking cards:
- Each row links to the related issue
- Severity hints reflect blocker status (active, nearly done, or cleared when the blocker is Done)
- Unresolved blockers sort above cleared ones
Planning impact
Blocked issues remain in backlogs and cycles, but planners should finish blockers first. Filters do not automatically hide blocked work — use relations during stand-up and planning reviews.
Update semantics
Saving relations replaces the full list for that kind on update — add and remove through the UI rather than expecting merge semantics on partial API payloads.
Next
Last updated on