Zach hey there! For me, inside a parent task, being able to auto-generate dependencies based on the sub-task order within (the second sub-task is dependent on the first being completed and so on). It could be for a parent task there's a feature like "auto dependencies" you could turn on at the parent task level that even when you drag and reorder tasks within it, it would auto update the dependencies. Also when you add a task it would add the dependency, too!

I’d like a feature in ClickUp that automatically creates sequential dependencies for tasks based on their current order in a list or view.

The problem:

When building linear workflows, most users create tasks in the exact order they should be completed. For example: Task 1 → Task 2 → Task 3 → Task 4. However, ClickUp requires manually adding each dependency, either through the Gantt view or through individual task menus. Even for a simple 10-step workflow, this requires 9–15 separate clicks, searches, and confirmations. For 20–50 tasks, the time commitment and error rate increase significantly. This makes dependencies far more labor-intensive than necessary, especially for recurring workflows, SOPs, onboarding checklists, and project templates.

What’s needed:

A simple action that tells ClickUp: “Create Finish-to-Start dependencies based on the order these tasks appear.”

Requested behavior:

Allow users to select multiple tasks or an entire list, then choose an action such as “Auto-generate sequential dependencies.” ClickUp should read the current order (manual sort or field-based sort) and automatically apply dependencies so that:

• Task 2 depends on Task 1

• Task 3 depends on Task 2

• Task 4 depends on Task 3

• …continuing through the entire selection

This mirrors exactly how most people think when building processes: the list order is the execution order.

Edge cases and clarifications:

• Should work with bulk-select or an entire list/group.

• Subtasks should follow the visible order; if collapsed, they can be ignored or included consistently.

• Dependency type: Finish-to-Start by default.

• Existing dependencies: Ideally have an option to preserve or overwrite.

• Closed tasks can be ignored unless specifically selected.

• If no sort is applied, use the manual drag-and-drop order.

Why this matters:

This feature removes repetitive work, reduces errors from missed dependencies, and dramatically speeds up building project templates and recurring processes. Most ClickUp users already organize their tasks in the correct order; this simply converts that order into functional dependencies with one click. It improves Gantt planning, reduces setup time, and aligns ClickUp with how real workflows are structured.

This would save project managers, operators, and onboarding teams significant time and make dependencies accessible to more users without forcing them into manual linking.

Hey Zach, you have addressed automatically setting dependencies at the task creation phase but setting dependencies for tasks that already exist within lists can only be done one task (and subtask) at a time.

Whether you use Gantt view or the Dependencies field in List view, this is incredibly tedious and is impossible to do in bulk.

As Pete Rakozy said above, being able to toggle something like "sequential dependencies" would simply be a game-changer for us.

Our organisation would LOVE something like a Sequential Sub-Task Dependency ClickApp.

Zach For us it's often about duplicated tasks. If we need to order materials to complete a series of connected tasks across different lists, it'd be ideal if we could set automations to not just link the duplicated tasks as we can now, but use dependency. At the moment you can only automate to a specific task which isn't much help for us and although the link has been more helpful, if you have more than one task linked it becomes difficult to know which task is being blocked and which is awaiting. So it becomes manual.

Equally, even just having a prompt that pops up when you duplicate a task "would you like to create a dependency?" would be a large step for us.