DocsTasksDependencies

Task Dependencies

Link tasks together with "depends on" relationships. ScenIQ automatically detects blocked tasks and visualizes dependency chains.

How Dependencies Work

A dependency means: "Task A depends on Task B" — Task A cannot be completed until Task B is done. When Task B is incomplete, Task A is automatically marked as Blocked.

Dependencies form a directed acyclic graph (DAG). ScenIQ prevents circular dependencies — you cannot create a loop where A depends on B and B depends on A.

Adding a Dependency from the Detail Page

1

Open the task

Click on a task from the list or graph to open its detail page.

2

Scroll to Dependencies

The detail page shows two sections: "Depends on" (tasks this one requires) and "Blocking" (tasks that depend on this one).

3

Click "Add Dependency"

A search modal appears listing all available tasks. Type to filter, then click a task to create the link.

Adding a Dependency from the Graph

1

Switch to Graph View

On the Tasks page, toggle the view to Graph.

2

Drag to connect

Hover over a task node's edge handle, then drag a line to another task node. Releasing on the target creates the dependency.

Direction matters

When you drag from Task A to Task B, it means Task A depends on Task B. The arrow points from the dependent task to the task it requires.

Removing a Dependency

On the task detail page, each dependency card has an unlink button. Click it to remove the dependency. Removing a dependency may automatically resolve a Blocked status if no other blockers remain.

Blocked Detection

ScenIQ continuously evaluates dependency chains. A task is considered blocked when any of its dependencies has a status other than Done. The blocked state is derived and automatic — you cannot manually set it.

When all dependencies of a blocked task are completed, the task automatically transitions back to its previous status (typically To Do or Active).

Viewing Dependencies

Dependencies are visible in multiple places:

  • Task Detail page — Dedicated sections for "Depends on" and "Blocking" with task cards showing status badges.
  • Graph View — Edges between nodes represent dependencies. Blocked tasks are visually highlighted.
  • Cross-Team Dependency Graph — Dependencies that span team boundaries are shown with distinct styling.

Multiple Assignees

Tasks support multiple assignees. When a task has more than one person assigned, all assignees are displayed as avatar badges on the task card and graph node. This is particularly useful for cross-functional tasks that require input from several team members.

Use the graph

The Graph View is the best way to understand complex dependency chains. It automatically arranges tasks using a Dagre layout algorithm for clarity.