Feature Requests

We would like the ability to make custom fields dependent on each other in the same way that tasks are now.

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.

Please add native enforcement for approvals and dependencies in ClickUp. ClickUp has helpful tools for statuses, custom fields, automations, dependencies, subtasks, templates, and views, but most track the process rather than enforce it. For formal project workflows, ClickUp needs to prevent work from moving forward when a required approval or blocking dependency is incomplete. Our structure is usually: * List = project container * Parent task = project summary and project metadata * Subtasks = project work items Because of this, locking one subtask is not always enough. If one subtask requires approval, the parent summary task, related subtasks, key metadata, and sometimes the whole List/Folder/project container may need to be locked until approval is granted. ## Current problem Approvals and dependencies can be bypassed too easily. We can use custom fields, statuses, assigned comments, and automations, but a manager can forget to mark that approval is required, or someone can move a task forward without the approval field being filled out correctly. Dependencies can show that one task is waiting on another, but users can still complete work out of order. A warning is helpful, but it is not the same as a hard stop. ## Requested functionality Please add configurable hard-stop enforcement for approvals and dependencies. If a task or subtask requires approval, it should not move forward until the assigned approver or approval team approves it. If Task B is waiting on Task A, and dependency enforcement is enabled, Task B should not move forward or be marked complete until Task A is complete. ## Approval needs Approval should be triggered by workflow logic, not only by a manually filled custom field. For example, approval could be required when a subtask enters “Ready for Approval” or “Complete,” when a task is created from a template, when a form has a certain request type, or when a workflow rule requires approval. Approvals should be assigned to a specific person, team, role, or approval manager. Only the assigned approver or approval team should be able to approve or reject. ClickUp should control who can change the approver, remove the approval, or bypass the approval. Trying to mimic this with custom field permissions would require many custom fields and becomes confusing and inefficient. It would be helpful to have an approval manager area where approval templates can define the workflow, approvers, order of approval, and whether one person, everyone, or a minimum number of people must approve. ## Locking needs When approval is pending, ClickUp should be able to lock the correct scope of work: * Only the task/subtask * The task/subtask and parent task * The task/subtask, parent task, and sibling subtasks * The entire List/Folder/project container * Selected related tasks * Key project metadata fields Locking should prevent bypass actions such as downstream status changes, completion, approver changes, approval removal, metadata changes, deletion, or moving the task/project. Comments, attachments, and discussion could still remain open. ## Rejection and dependency behavior If approval is rejected, the task should reopen for changes, move to “Needs Revision,” require a rejection reason if configured, notify the right people, and allow resubmission. If dependency enforcement is enabled, dependent tasks should remain blocked while the rejected task is being revised. This prevents users from skipping the approval path and continuing the project anyway. Dependencies should support an “enforce” option, not just warnings. Helpful options would include: * Prevent a waiting task from being completed until the blocking task is complete * Prevent a waiting task from moving to selected downstream statuses * Prevent dependent sibling subtasks from moving forward * Prevent the parent project summary task from being marked complete while blocking items remain incomplete * Allow admins to choose warning vs. hard stop * Record any admin override in history ## History and reporting Approval and dependency enforcement should be auditable and reportable. ClickUp should track approvals, rejections, approver changes, bypasses, overrides, rejection reasons, and dependency blocks. Approval/dependency status should be visible on the task, subtask, parent project summary task, and available in views, filters, dashboards, reports, and automations. ## Why this matters Without enforced approvals and dependencies, we rely too much on people remembering the process, filling out fields correctly, and not moving work forward too soon. This would improve consistency, accountability, auditability, governance, reporting, and compliance. Priority: High. Approvals and dependencies need to do more than warn or track; they need to prevent a task, subtask, or project from moving forward until the required approval or blocking work is complete.

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

Currently, it's very difficult to manage task-level constraints and dependencies without heavy reliance on calculated fields, complex automations, and SuperAgents.The recalculating dependencies doesn't fix this timeline build problem. Since ~1980s, standard project management methodology best practices have included specific ways to handle tasks that have active levers that can or cannot be turned at different parts of a project: Start-Start dependencies Finish-Start dependencies Start-Finish dependencies Finish-Finish dependencies Without the ability to set these types of indicators on tasks, visibility into things like Critical Path dependencies is reduced. Also, this change would enable true capture of dependency rescheduling (or forecasting) and the impacts of delays, with high reporting accuracy. This should align well with the baseline Gantt features recently rolled out. When a project plan has hundreds (or thousands) of line items across many teams in Enterprise projects (especially in tech), such visibility and accuracy are critical.

There should be an option for 'Use subtasks dates' to be constantly on for a selected parent task. At the moment 'Use subtask dates' clears on every reload of the page, which leads to scheduling errors when a parent task has dependencies down stream.

Is there any way to write a due date in this way: Due "3 days before XYZ Step"?

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

It would be beneficial to visualize dependencies between tasks (also folders and lists) visually. This would enable easy identification of bottlenecks and critical paths.