Browse documentation

Link tasks

Distinguish related and blocking relationships from Git stack ancestry.

Task links record direct relationships between tasks in the same project. They are separate from Code stacks: links never change branches, Git ancestry, or restacking.

Two link kinds are supported:

  • Related is symmetric and informational.
  • Blocks is directed. A blocks B prevents B from merging while A is open, but B can still be taken, edited, submitted, and reviewed. Closing A—merged or unmerged—clears the gate.

Create links with:

rp task link A B
rp task link A B --blocks

Active blocking chains are prohibited: a blocked task cannot block another task, and a task that blocks another cannot become blocked. Multiple independent blockers may block one task, and one unblocked task may block multiple tasks.

Remove either kind with a guarded action and an audit reason:

rp task unlink A B --text <reason>
rp task unlink A B --file <path>

rp task show and task pages list direct Related, Blocked by, and Blocks relationships. Browser task links are read-only and navigate to the visible counterpart task; create and remove links with rp. Links to tasks the viewer cannot read are omitted.

Project task.write holders may add links between visible tasks. Otherwise, a task creator/current owner may anchor a Related link on their task or block their own task on another visible task; report-only accounts are limited to two tasks they created. Removal requires task.manage, uses pinned guarded-action execution, and rejects stale confirmations.

Related add/remove activity is recorded on both task timelines. Blocks activity is recorded only on the blocked task, whose owner is the only relationship owner notified. Readiness text never names blocker tasks hidden from the viewer.