Task Dependencies in TaskRely

Real work is rarely a flat list. The design has to be approved before development starts; the API has to ship before the frontend can use it. Dependencies let you say that directly on the task, instead of leaving "what's this actually waiting on" to get answered in a chat thread somewhere else.

Blocked by, and blocks

Open a task and you'll find a Dependencies section with two sides. Blocked by is where you add tasks this one is waiting on - click it and search for a task from the same project. Blocks is a read-only mirror: it fills in automatically the moment another task lists this one as something it's waiting on, and you don't add anything there directly. Remove the link from either side and it disappears from both.

What it doesn't do

A dependency is informational, not a hard gate. A task can still be dragged to Done even if what it's blocked by isn't finished yet - TaskRely shows you the relationship, it just doesn't stop you. The one thing it does stop automatically: a circular dependency. If Task A is blocked by Task B, you can't turn around and make Task B blocked by Task A - the system checks for that before saving the link, even through a longer chain.

Where it shows up

Dependencies live on the task detail view, next to subtasks and comments. They're not shown as a badge on the card itself, so if you want to check blocking relationships while scanning the board, you'll need to open the task. For sequencing across a whole project, Timeline is the better view.