Feature Requests

I shouldn't have to create a task, apply a template, edit the task, then save the template. I should be able to edit the template directly in the template centre, then close the template centre when finished.

Our team works with different divisions and brands, so we need to set up separate dashboards for each of these groups to view privately. We would love the ability to save templates for dashboards/widget setup since we need to collect the same types of information for each group but with different filters (so they can see they're specific stats.) This would help us cut down setup time tremendously within Clickup.

Please add an option to disable the ‘Do you want to create a template draft?’ popup after creating a task.

I would love it if I could favorite the "Template Center" or at least my "Workspace Templates" onto my favorites bar for easy access.

Currently you can only have 5 pinned task templates. It would be great to be able to pin more, or have an easier way to access the rest of the templates for a list besides searching for them in the template center. That puts a big barrier to using the rest of the templates we need.

Being able to set a default task template based on the custom task type in ClickUp3.

From Support: It would be nice if edits to our Views applied to previous versions. This would prevent us from needing to update hundreds of Templates manually in a larger organization.

It would be nice to be able to load templates to multiple tasks at once. I would like to be able to select all tasks I want to apply the template to and load the template to them quickly.

This might be be dependent on https://feedback.clickup.com/feature-requests/p/let-subtasks-inherit-all-custom-fields-of-parent-tasks , but I would like the ability to prepend or append a task's custom field value to the task name. Right now, I have a task template that has about 30 sub-tasks. When I create more than one parent task using that template, linking other existing tasks to the new sub-tasks is basically impossible through the dependency selector on the task because all instances of the template tasks share the exact same name, and no breadcrumbs exist to show where the sub-tasks/tasks exist. The attached image shows an example of the problem I'm talking about. I am unsure how to determine the correct sub-task.