Feature Requests

From Josef: Remapping subtasks from parent task due date is great. But we also need it the othe way: whenever a subtask is delayed and rescheduled then the parent task due date should be updated according to new due dates for subtasks. Ideally the parent task due date could be auto-updated to max(due date for all subtasks) or due date for the last subtask in a chain of dependencies.

Hi ClickUp team, I’m running into an issue with Dependencies and “Done” statuses, and I’d like to request an improvement to how dependency unblocking works. The problem In ClickUp, a task that is “blocking” other tasks will cause the dependent tasks to become unblocked as soon as the blocking task is moved into any Done status. In my workflow, we use Done statuses like Client Review to indicate “my work is done, but we’re waiting on the client.” This status should not unblock downstream tasks, because the next production step should only begin after the client has reviewed and approved the work. Right now, if I move a task to Client Review (Done), ClickUp automatically unblocks the next step. That creates incorrect “open” work and causes premature handoffs. Example workflow Each production step is its own root-level task (not subtasks): Recording -> Editing -> Mix Prep -> Mix -> Master Statuses: Not started: Open (Not Started group) Active: In progress, Waiting Done: Client review, Invoice Closed: Closed/Complete Some steps require client approval, others do not. I want Client Review to behave like a “done-ish / waiting” stage for workload purposes (not overdue, not active work), but I do not want it to unblock dependencies. Requested solution Please add an option to control dependency unblocking behavior, for example: Workspace / Space / List setting (or per-status option): “Unblock dependencies when blocking task moves to:” Done statuses Closed status only Ideally this could be configured per status as well, for example: Client Review: does not unblock Invoice: can unblock (optional) Why this matters This would reduce admin overhead and prevent false “ready to start” work, while still letting teams use Done statuses for “waiting” states that should not count as active workload. Thanks for considering this.

Many times when scheduling I need two tasks to finish at the same time and want to know the required start dates. I would suggest that additional dependency options other than "blocks" or "is blocking" like Start/Start Start/Finish Finish/Finish and +/- days modifiers are needed.

Allow team members to set leave or vacation dates, and prevent others to assign tasks on those dates? (Submitted via Intercom)

Right now there is only option to use task name when creating dependencies between (sub)tasks. THis is problematic when while we use a template for new clients onboarding thus the task names are idential (just the header task indicates which client it belongs to). We need to have the option to use task ID or/and task URL when creating the dependencies (worked in older UI)

There have been nice updates on due dates, but I'd like to be able to set them and automatically update them by dependency. For example, once Task 1 occurs, Task 2 is due within 48 business hours. So, when I mark Task 1 complete, I'd like the due date on Task 2 to update to 48 business hours later. This allows the template to automatically update.

Comment from support: When I change the date of a task to a later date, the dependencies are moved back to a later date too, but when I move the date of the task to an earlier date, the dependencies don't change?

When a parent task is updated, update subtask start dates as well as due dates.

SS and FF task dependencies are essential in my consulting projects. Like to request for these to be available soon (like the next upgrade).