I'd like to be able to have templates with certain fields you're prompted to select a value for when using the template, and have those values populate everywhere the field is used in the original value.

For example, I have a project list for each major trade show, and a separate list to serve as our events calendar with a task representing each event. In my event list, I have automations to set the Business Unit custom field for every task moved to, added to, or created in the list, and to set a custom relationship value to relate the task to the calendar task associated with that list. Every time I use my template, I have to go through and replace the trade show task and business unit field in several places.

If I could apply my template and be prompted to say which business unit and trade show task this list's automations etc. should go to and have anywhere in the template that references those fields populated accordingly, that would save a lot of work.

Alternatively, if I could set these values for all tasks in a list in a way other than automations or AI, that'd be helpful.

I see some similar feature requests and have upvoted them, but mine applies to both recurring tasks and task templates so I wanted to flag it again for ClickUp's consideration. --

WHAT I'M ASKING FOR

A way to reference custom field values directly in task names -- something like {{Client}} or {{Month}} -- so that when a task is created from a template or recurring schedule, the name fills in automatically with the right context.

CONTEXT ON WHY THIS MATTERS

Right now, when I use a task template or set up a recurring task, every generated task gets the same generic name. That means my list ends up with three tasks all called "Analytics Report" — and there's no way to tell at a glance which one is for which client. I end up renaming them manually every time, which defeats the purpose of having templates at all.

WAHT IT WOULD LOOK LIKE IN PRACTICE

Say I have a recurring subtask under my Inasmuch Analytics project. Instead of naming it "Draft Analytics Report Summary" every month, I'd name it "Draft {{Month}} Analytics Report Summary," and it would automatically become "Draft January Analytics Report Summary," "Draft February Analytics Report Summary," and so on.

Same idea with templates: instead of "Monthly Check In," the task name becomes "{{Client}} Monthly Check In" — so when I apply the template for different clients, I get "Nature Day Spa Monthly Check In" and "Olive Lane Interiors Monthly Check In" as separate, clearly labeled tasks.

WHY THIS SEEMS DOABLE?

ClickUp already supports dynamic text in automations, so the underlying logic seems like it's already there -- this would just extend it to task name fields in templates and recurring tasks. allow custom field values to be merged into task names using a variable syntax (e.g., {{Field Name}}), so that templated or recurring tasks automatically reflect the relevant context -- like client name or reporting period -- without manual renaming.

When creating a task from a template, allow subtask names to automatically populate using the parent task’s title (dynamic variable), so teams do not need to manually rename subtasks every time.

Problem: Today, subtasks created from templates keep static names. For workflows where the parent task title is the key identifier (product name, campaign name, client name, SKU), every task created from the template requires manual subtask renaming. This is repetitive, error-prone, and reduces template usefulness at scale.

According to the assignee and people column, map automatically for execution person, project manager, partner, sponsor...

We would like the ability to define and add custom “roles” as placeholders for assignees in task templates. As template creators, we should be able to decide what roles to add (for example: “QA Lead,” “Client Owner,” “Designer,” etc.).

When applying the template, the user should be prompted to map each custom role to a specific person. All tasks with that role as assignee would then be automatically assigned to the mapped user.

Benefits:

Makes templates more flexible and reusable across teams and projects.

Reduces manual reassignment of tasks after applying a template.

Supports larger teams and cross-functional projects where roles change per project.

I like the functionality to set dynamic assignees in Automations. This functionality should be available in task templates as well. This means, when I apply the template the dynamic assignee kicks in and sets the assignee according to their role.

I would love for there to be an option to have the ability to insert a 'dynamic variable' merge tag when applying a template so that the subtasks inherit the parent task name(followed by the subtask name).

Example:

Task: [Task Name - John]

Subtask: [Task Name - John] - set up calendar invite

Currently you can only do this through automations.

This would save a lot of copy and pasting, make notifications clearer and save on boarding time with new projects.

is it possible when a template is applied, to have all of the subtasks automatically take the parent task title as a prefix to the subtask's title? or a specified portion of the parent tasks title. example: parent task title 12345 - gym; the subtasks in the applied template would automatically take ''12345 - gym'' or ''12345'' and make this the prefix to the subtask titles

Be nice to have per list/task roles best for templates so we can assign a user to a role and it will assign them the proper tasks dynamically or if in a list we assign a user to a role if the list or task has one it will assign them to all tasks for that role.