Feature Requests

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

If you reschedule a task and there is sufficient slack time do not reschedule the dependent tasks. (Submitted via User)

In construction project management, tasks (e.g. "Wall Framing" or "Roof Sheeting") span days or weeks. Multiple people rotate across these tasks on different days. A supervisor needs to assign specific people to specific tasks on specific days, and workers need to see exactly what they are doing each day. ClickUp currently has no way to say: "Tyler works on Wall Framing on Monday and Tuesday, then Roof Sheeting on Wednesday. Jared works on Wall Framing all week." The existing options fall short: Work by Day lets you allocate hours per day on a task, but it only affects Workload view. It doesn't show on the worker's Calendar, Planner, or mobile Day Card, so field staff can't see their daily schedule. Multiple assignees on a multi-day task puts every assignee on every day, with no way to specify who works which day. The only workaround is creating a subtask per person per day with a time estimate, which works but creates massive overhead for a supervisor scheduling 5-10 people across 3-5 jobs for a full week. ## What We Are Asking For A drag-and-drop scheduling feature where a supervisor can: Drag a person onto a task for a specific day (or range of days) from a Workload or scheduling view. This would assign that person to that task for those specific days only. The assignment shows on the worker's Day Card and Calendar so they can open their phone and see: "Monday: Wall Framing at Job X. Tuesday: Wall Framing at Job X. Wednesday: Roof Sheeting at Job Y." The Workload view updates automatically to reflect the hours allocated to that person on those days, so the supervisor can see capacity filling up in real time as they schedule. No subtask creation required. The parent task remains a single task. The per-day, per-person assignments are a scheduling layer, not separate tasks. Essentially: one task, multiple people, each person assigned to specific days, visible on both the supervisor's Workload view and the worker's daily schedule. ## Who This Helps Construction companies, trades, agencies, consulting firms, and any team managing people across long-running tasks on multiple concurrent projects. This is standard functionality in traditional project scheduling tools (e.g. BEAMS, MS Project) and is the single biggest gap preventing ClickUp from replacing them for field-based industries. ## Current Workaround Create a subtask per person per day with a single-day date and time estimate. This works for Workload view and mobile Day Card visibility, but creates dozens of subtasks per week per job, making it impractical at scale without significant administrative overhead.

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.

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.

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.

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.

[From support] Calendar (Time view), I set mine to Week View and with hours showing, but it shows 0:00 from the top so I always have to scroll it down to see my common working hours wchich is like 9AM - 7PM. Is there something we can do to set the hours that show in the Calendar (Time view)?

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?