Feature Requests

Description: Currently, in Gantt view, we cannot drag and drop tasks into other tasks to make them subtasks. It would greatly improve workflow and planning efficiency if users could drag a task onto another to instantly convert it into a subtask — similar to how it's done in List view. This would make task structuring in Gantt more intuitive and reduce the time spent switching between views just to organize subtasks.

Row height control Just like you can zoom in/out to compress column widths in Gantt view, it would be great to have the same control over row height. A compact/dense mode would significantly reduce the need to scroll, especially when managing multiple projects (lists) in one overview. Currently there is a lot of vertical whitespace between task bars. Horizontal gridlines toggle A simple on/off toggle for horizontal lines between rows would improve readability, making it easier to distinguish which bar belongs to which task — especially in a dense, multi-project view. Day lines in month view When zoomed out to month view, vertical day lines disappear. It would be helpful to keep day indicators visible even at this zoom level, similar to how week lines remain visible when zooming out further. Why this matters We manage multiple projects across several lists and need a single planning overview. Right now the Gantt view has too much negative space and loses day-level detail when zoomed out, making it hard to replace a compact Excel-based planning. These small UI improvements would make ClickUp Gantt viable as a full planning replacement.

The Gantt view doesn't take the aggregated time estimation of the subtasks. I'd like to work on a clean representation, hidding subtasks (but even wuthout doing that), dragging my 1000H taks just put it in 1day slot. I'd hope the full perdiod can be represented, from the starting date I'm putting and consedering the estimation time, the expected day the task will end.

Nice to have features for the future of the ClickUp Gantt Chart

It would be nice to be able to edit the settings as pageformat, timerange etc. when exporting a Gantt-chart as PDF.

It would be great if tasks could be grouped (and collapsed) in a Gantt view the way they can be in a list view. This would be particularly useful for custom fields. For example if you have a custom dropdown field for region, period, customer, product, program, etc. it would be great to be able to see all tasks with each dropdown field value grouped together.

When exporting a GANTT chart, I enter the Start Date and the End Date but when I export these dates they are not respected and I have to postpone or anticipate to get by and export the chart I want to view.

It would be very useful if in the GANTT view all activities were divided by a line to better read which activity the bar is linked to. It would also be useful to have lines that divide the folders, perhaps with a more marked stroke. Practically, now, if I export and print a GANTT, I have to use a ruler to understand what activity the bar on the right is linked to. If there were lines dividing the activities, everything would be more readable. Thank you.

It would be very useful and impactful if the activity bars in the GANTT view were colored and filled based on the value of the relative current progress.

ClickUp Gantt currently relies on a single timeline (Start/Due), which limits real project tracking. Problem Many teams track: • Planned Start / Finish (Start & Due dates) • Actual Start / Finish (custom fields) But: • Only one timeline can be shown • Custom date fields cannot drive Gantt bars • Baselines are static and don’t support live comparison Request • Allow multiple date sets per task (planned, actual, etc.) • Allow selecting which fields drive Gantt bars • Allow overlay / dual timelines in the same row • e.g. Planned (solid bar) vs Actual (overlay or patterned) Why this matters • Enables true planned vs actual tracking • Removes workarounds and misuse of baselines • Aligns with tools like MS Project / Primavera Limitation of “Date done” “Date done” should not be used as Actual Finish: • It is a non-customizable field • Tasks are often closed later than work is completed • It does not reliably reflect real execution * Teams need separate Actual Start / Actual Finish fields, and the ability to visualise them alongside planned dates