Feature Requests

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.

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.

It would be great to have the ability to change task names through automation. When someone submits a form, it would be ideal to have the task name change to a relevant field submission from the form or similar.

When you create a task that repeats as a new task, it does not maintain the task type you assigned it.

I’d like to suggest an improvement for automations involving custom fields of the "Date" type. Currently, when configuring an automation, the "From" and "To" fields only allow selecting specific dates rather than defining a date range. Even though it’s possible to select a date range visually, the automation only triggers based on the final date in the range, not the full range itself. This significantly limits the flexibility of automations based on date conditions. Having true date range functionality would greatly improve automation workflows, allowing triggers to be applied to any date within the selected range, not just a single date. If this is not an intended limitation, it might also be a bug worth investigating. Thank you for considering this request, and I’d appreciate any updates on whether this enhancement could be added to the roadmap.

Please create an option to automate removing a task from additional list

The ability to apply a list template via automation. e.g. a "project" (task) is created in a projects overview list. The automation would then apply a list template for that project. Being able to also use the "project" (task) name as the list name automatically would great.

From Support Ticket: I can't automate status change or anything based on email thread (eg WHEN New Email received THEN change status)

There are usage caps on automations that are spread across an entire workspace. With many teams using automations in many different ways, it would be very useful to see which automations (grouped by space/folder/list/etc) are gobbling up the most of the usage limits. This way, a company can internally coordinate the best way to budget automations.

Hi, I designed my Epic concept, (it could to be used by collections, themes, objectives...) Firstly, I create a task, and set a custom field as type "Epic", to be classified. Then, every task that is necessary to achieve this epic, is added as an checklist element. I call them "children", and the Epic task, is "Parent". The children tasks use a custom field of Task Type to link to the parent task (Epic), so, when a task is done, I go to the parent task using this custom field "parent", and mark the element in the Parent's checklist. So I can see the progress of the epic. This solution, could to be nested and to have several levels of parents. For example: 1.- I create a task as an general objective. This objective has some Epics tasks, and each Epic task will use the "parent" field to link to the Objective task. 2.- A children task of an Epic could to be a group of tasks... The problem, is that we need a lot of work to maintenance the tasks. It would be so useful if ClickUp add a new type of task list (subtasks, checklists and the new "children" for example, or a similar solution), so the progress is managed automatically, and it would be easier to manage the children tasks. Finally, in my Goal, I include Epics or Tasks to achieve it, but I have a List View only of Epics to monitoring the complete progress of all our epics. Note that I read all proposal and solutions in tutorial, suggestions... but nothing was really useful; so it is the best solution for me. I attached images about my proposal that I use and it works for my team: