Using task dependencies
TL;DR: Task dependencies let you create connected workflows where the next task only appears on your dashboard once the previous task is marked as done, useful for sequential processes like client onboarding.
Who can do this
Any Uku user who can create or edit tasks
Tasks must already exist in Uku before dependencies can be assigned
Editing templates and work plans requires appropriate permissions
Project Management Requires Dependent Tasks
In Uku, you can set task dependencies. Dependent tasks are a great way to create connected workflows. Marking dependence means that the next task will appear on your dashboard only when the previous one is marked as done. For example, it is good to use dependent tasks when onboarding new clients.
Important: Marking dependence means that a task depends on the previous task. The previous task (the task that you set a dependency on) must be marked as finished; then the next task will appear on your dashboard.
Logic
Related tasks must be in a logical order by date. For example, if task B depends on task A, the start date of A cannot be later than B's.
Tasks that are dependent on each other must have the same recurrence. For example, a monthly task can only depend on other monthly tasks, not weekly ones.
Example
The Submit documents task is related to the Receive documents task. When Receive documents is marked as done, Submit documents will appear on the dashboard. Before marking it done, the task will not appear on your dashboard.
How to create a task dependency for a one-time task
Before assigning dependencies, ensure you have entered all the necessary tasks into Uku.
Open the task you want to assign the dependency to (the task that should appear after the first task is marked as done).
Select the dependency icon in the task footer to set the relationship. This opens the Depends on field. The dropdown lists this client's tasks within 45 days.
Select one or more tasks from the dropdown that must be marked as done before this task. When selecting multiple tasks, all selected tasks must be marked as done for the dependent task to appear on your dashboard.
How to create task dependency in templates and work plans
Create dependency tasks in a template or work plan assigned to the client to avoid manually entering the dependencies. Creating them in the template or work plan follows the same process as with one-time tasks.
Important: Dependent recurring tasks can only be in the same period, e.g., week, month, or year.
Troubleshooting
The task I want to depend on does not appear in the dropdown. The Depends on dropdown only lists tasks for the same client within a 45-day window. Ensure the prerequisite task is assigned to the same client and falls within this date range.
A dependent task appeared on the dashboard before the prerequisite was completed. Verify that the dependency was properly saved by opening the task and checking the Depends on field. If the field is empty, the dependency was not set.
I cannot set a dependency between two recurring tasks. Dependent recurring tasks must share the same recurrence period (e.g., both monthly or both weekly). A monthly task cannot depend on a weekly task.
The dependency icon is not visible in the task view. The dependency icon is located in the task footer area. If you do not see it, ensure you have the correct permissions and that the task is in edit mode.