Feature Requests

It would be very practical to click and drag a dependency between the options in this frame, without having to delete and re-include them in the “WAITING” section if you added them incorrectly.

The dependencies are important for me and my team to have, but seeing it on the gantt often overwhelms some stakeholders. I'd like the ability to toggle them off and on from the gantt view and for that toggle to also determine if they are displayed in a PDF export of the gantt.

problem When I log tasks into blocks of time in ClickUp Planner (e.g. 2 hours in the morning, 3 hours in the afternoon), the system does not check whether I have already used up my entire hourly budget for this task. It simply creates new blockers even if I exceed the task's time quota. As a result, I mistakenly schedule more hours than would be allowed in the task — and the planning becomes inconsistent. Desired behavior/ solution I would like an extension in Planner where ClickUp checks when creating a blocker: Remaining budget of the task: How many hours are left for this task (estimated hours minus hours already booked)? Blocker limitation: If a blocker exceeds the remaining budget, it must either not be created or it is automatically reduced to the remaining budget. Warning/Note: When I try to block more hours, a message appears: “Remaining budget of this task = X h. The blocker has been cut/cannot be created. ” Visual presentation: The task card or in the planner sidebar shows how many hours have already been planned and how many are still available (e.g. “planned: 5 h/budget: 8 h/rest: 3 h”). Also desirable: Overdraft with permission: In exceptional cases, you should perhaps be allowed to overdraw (e.g. when working overtime), but only with explicit confirmation — i.e. not tacitly. Benefits/Added value for users & ClickUp prevents overbooking and inconsistent planning promotes accuracy in time planning & resource allocation reduces manual readjustments and errors makes ClickUp Planner more attractive for teams with strict time budgets strengthens ClickUp's position over competitors with such features Reference tool: Scoro, offers a function that shows the remaining time per task in the planner so that you can schedule work accordingly without exceeding the limits.

I wanted to bring up a usability issue related to task dependencies and subtasks. Currently, when attempting to close a task that has unresolved dependencies or incomplete subtasks, ClickUp displays a warning — which is great. However, if a user chooses to proceed and close the task anyway, there is no visible indication afterward that unresolved dependencies or incomplete subtasks still exist. This can lead to confusion or miscommunication within teams, as it may appear that all related work has been completed when that’s not actually the case. Feature Request: It would be helpful if closed tasks that still have unresolved dependencies or incomplete subtasks could visually indicate this status — either via a warning icon, tag, or a small banner/note within the task view. This would help users quickly identify that there are still pending items linked to the task, even if it's marked as complete.

I'd benefit immensely from being able to define a task with start date and duration instead of start date and end date. Combined with the ability to set the task list/gantt chart to intelligently never assign something on the weekend, this would allow me to shift dates without having to readjust the end dates for every task that now falls on the weekend or used to fall on the weekend.

"I was a Motion user, and what I liked about the template was that for each stage—which in ClickUp we can think of as the main task—I could use the start and end dates of the task to configure the start and end dates of the subtasks. i think it would elebvate the planning feature in Clickup! When changing the date for a task, I wnat to make sure that when I change the date of a task teh dependt tasks change by the same number of days!

There is currently no reliable way to define a fixed “Project Start Date” in ClickUp that can be used as a reference point for formulas, automations, and AI. This is a core gap in project planning. We can't calculate project-specific week numbers for tasks (e.g. "This is Week 3 of the project"). The existing “Week” value in Calendar or Gantt views is based on the week of the year, which is not useful for internal project timelines that start at different times. We can’t configure task start/end dates relative to a project start point (e.g. "Start this task 10 days after project kickoff" or "Trigger 3 days before project end"). This is essential for automating templates and milestone plans. Right now, we’re forced to use hacky automations, patchy formulas, or manual date input — which defeats the purpose of having a project management platform. Even recent improvements like calculating end dates from duration are partial fixes that still don’t solve the root problem. Please give us a static project reference date — ideally using the List Start Date — that is: Globally accessible in formulas Usable in automations and templates Referenceable by AI agents Able to drive dynamic date logic across tasks This is Project Management 101 — every professional PM tool anchors schedules to a static start or end date. This one change would unlock powerful planning capabilities, simplify templates, and reduce manual overhead.

I'm looking to set a hard due date for milestones which prevents any slack beyond this point. Clickup doesn't seem to have this capability, the slack for one of my handover dates carries over until the due date of my last task, which is in a different list. I can see this has been requested by other users, but still no solution?

Primary task estimated completion date is allowed blank and automatically filled in by the furthest out subtask. The primary task completion date is dependent on subtasks. A common feature elsewhere. The impact of a subtask going long is immediately seen in all views but particularly in Gantt. With many team members working from disparate locations, the ability to impact the project by a simple task going long is not to be overestimated.

When a Parent Task has a due date set, subtasks should not be allowed to have due dates that extend beyond the parent’s due date. Ideally, there should be an option you can enable — one that enforces this restriction by default, but still allows flexibility when needed by manually overriding it.