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.

Assign a due date based on a number of business days ie be able to click Skip Weekends when automating a due date

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

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.

Option to have different days set as the weekend.

I've been using ClickUp for 6 months now and at least twice per day I end up frustrated. Don't get me wrong, it's nice to look at, has plenty of options to customize it however you want for whomever you want, and it makes things understandable at a glance (if properly set up). But all that ends up buried under the bugs, inconsistencies, and overload of information. I'll list things that need improvement ASAP: Tickets set on the Gantt cannot be removed from it once they are set on the timeline, you need to delete the whole ticket. This adds to the fact that a left click allows you both to move the timeline and also sets a ticket into it making it very easy to miss-click; You cannot add spaces between tickets in the Gantt which makes it convoluted once you hit a threshold of tickets and dependencies; Tickets seem to disappear when you add them. I've had dozens of tickets written down and when I go back to look at them they were not saved. You cannot "move" (three dot options) multiple tickets selected with the multi-select tool. You need to go one by one. Each time you click on a ticket's square marking (that states where it is on the line ie backlog/working on/etc) it throws a notification that covers the same square marking making it tedious to modify several tickets one after the other. Columns taken from the library sometimes are added but they don't appear. And you can't re-apply the column because for clickUp the column has been added. Sprints are a hell of a task to modify. They take for static timeframes (a straight week/2weeks/etc) which makes it really hard to accommodate for the particularity of each week The previous issue is exacerbated by the fact that it's impossible to save date changes. I've gone to each sprint when needed and altered the default date to fit the week, 60% of the time it doesn't save the changes. Sometimes it allows you to change the date of the sprint but it still ends the sprint with the previous default values, so you have an expired sprint that hasn't actually expired making a mess of whatever organization you want to have. The "Sprint" column for tickets sometimes doesn't save the sprint. I've had to hit f5 several times to see if changes were being saved and re-apply the attribute just because every time I had set it it disappeared in front of my eyes.

It would be nice to have to option to add a countdown to the due dates on tasks, especially in the list view so in addition to seeing the due date you could also see maybe "Due In" as a column heading and then "3 days" or whatever for when it's due. Perhaps this could be available in other views as well. Obviously we don't want things too cluttered so maybe this can be an added option for those who want to use it?

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?