Feature Requests

I would like to be able to create date ranges based on custom dates so that I can build calendar views that are not based on start/due date fields. My use case is that I'd like a calendar view showing when campaigns are LIVE, so we can easily see them, see what campaigns overlap, etc. Right now, you can create this view, but only based on start/due date fields, but these dates are not always the "campaign live dates", they are changing due dates based on the stage that the project is at. Aka start date = when work started on the project, and due date = when everything (including post live tasks) conclude, not the actual dates of the campaign.

It would be very convenient to have the ability to have subfolders. I use folders for classifying projects. For example, Projects would be a Folder name. 2019 Projects would be a Subfolder name.

Consider the following situation: There are 3 Lists A, B, C each with a column called "client name" There is another List D which has a list of 1000 client names. I created a relationship field such that the column "client name" in Lists A-C can access client names in List D. However, since this relationship is on a list to list level, the information is lost incase a task is moved between List A-C. Is there a solution to this? Is there a way to create a relationship, such that the "client name" value is not lost when we move the request from one list to another?

It'd be dope if clickup AI would support https://modelcontextprotocol.io/ . With that its agent could instantly integrate with a ton of tools without you having to do first party integrations in the first place. Some tools like cursor.ai just allow you to paste in an MCP link and bam, you have it in your agent. Support this ONE thing and save time integrating all the others. Let your users do the job and give them the power to integrate properly.

I would like to be able to set the estimated time for a number of my tasks at one time.

I'd like to have an automation that is triggered by the time in a status. For example: When task has been in Review status for 5 days, add tag. Another example for user support: When task is In Progress status for 10 days, send email template.

It would be really helpful to be able to add a relationship between the task that triggered an automation, and the task that was created as a result of that automation. This would allow my team members to see the connection between our master tickets and the individual tasks that get created with automations as they move through our workflow without manually setting each relationship after the automation triggers.

Right now, automations are done at the list level. This gives far less control since every task in that last would be subject to that automation. I am suggesting that automations be done at the TASK level so that you can set something for just 1 task.

Currently, there's no option to enable AI tools for specific users only, and some users might not need this feature at all. Please consider introducing a feature similar to GitHub Copilot integration: the organization is billed monthly for the number of seats selected for given users.