Agiled Docs

Task dependencies show that one task is waiting on another task. Use them when the order of work matters inside a project.

Where Dependencies Appear

Dependencies are available from project task details. Open Productivity > Projects, select a project, then open a task from the project task list or board.

The task detail panel includes a Dependencies section where you can add or remove tasks this task depends on.

Add a Dependency

Open the project task.
Find the Dependencies section.
Choose another task from the selector.
Select Add.

The selected task appears as a dependency with its title and status. Use this to show that the current task should wait until the other task is completed or unblocked.

Add a dependency only when it changes what someone should do next. If the tasks are merely related, link them in a comment or project note instead.

Use dependencies for blocking order, not for general priority. A high-priority task can still be independent if someone can start it now.

Before adding a dependency, check whether a milestone would communicate the phase better. Dependencies are best for task-to-task blocking; milestones are better for broader delivery checkpoints.

Choose the Right Direction

Add the dependency to the task that is waiting. If Design review must finish before Publish page, open Publish page and add Design review as the dependency.

The dependency should answer: "What must be finished before this task can move forward?"

Remove a Dependency

Use the delete action beside the dependency when the relationship no longer applies. Removing a dependency does not delete either task; it only removes the blocking relationship.

Remove dependencies during cleanup when the blocker is complete, cancelled, or no longer affects the waiting task. Old blockers make project boards look more stuck than they are.

Dependency Rules

Agiled prevents dependency loops. A task cannot depend on itself, and adding a dependency that would create a circular chain is blocked.

Keep dependencies focused. If everything depends on everything else, the project becomes harder to read.

During project review, filter or scan for blocked tasks and open the dependency task. Update the blocking task's status, owner, or due date so the dependent work does not sit without a clear next step.

Communicate Blockers

When you add a dependency, also update the blocker task with an owner, due date, and clear next action. Dependencies make blocked work visible, but they do not assign responsibility by themselves.

Dependency Review

Before a project update:

check blocked tasks
confirm each dependency still matters
update the blocking task first
add an owner and due date to the blocker
remove dependencies that no longer affect the work

If many tasks are blocked by one item, raise that blocker in the project status instead of leaving it hidden in individual tasks.

After the blocking task moves, notify or mention the owner of the dependent task if they are expected to start work immediately.

Common Mistakes

Adding dependencies between tasks that are only related.
Adding the dependency in the wrong direction.
Leaving blocker tasks without owners or due dates.
Keeping old dependencies after the blocker is complete.
Using dependencies instead of project milestones for broad phase planning.

Task Dependencies