Variables (dynamic values) in Templates (task name, description, assignee etc.)
Allan Nygren
We launch products that have different names and would love the ability to have variables within project templates for task names and descriptions.
For example, when you spin up a new project for launching 'Project Alpha', it would be great to be able to put the Project Name into a field and have that populate through all the tasks with Project Name in the task title or description.
Log In
Lily Chan
Merged in a post:
Add roles to templates
Julien Pader
According to the assignee and people column, map automatically for execution person, project manager, partner, sponsor...
Lily Chan
Merged in a post:
Please add dynamic, user-defined role placeholders for assignees in templates, so we can create and assign our own roles and map them to users when creating new projects from templates
Nicky Salido
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.
Lily Chan
Merged in a post:
Dynamic assignees in task templates
Melanie von Schorlemer
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.
Lily Chan
Merged in a post:
Inherit/Apply Task Names to Subtasks when a Template is applied
Hannah Nurse
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.
Lily Chan
Merged in a post:
Automate subtasks to inherit parent task name as prefix
J
Jamie Phatthammachack
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
Brenno Vicario Nicolau
I have to create a dropdown custom field solely to use it as a condition—assigning an option to each task I want to automate. It's extremely frustrating! Why not apply the same logic used in the "Filter by Task Name"/"Search in Task Name" feature to automations as well?
Lily Chan
Merged in a post:
List/Task Roles
Lesford “LJ” McKenzie
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.
Lily Chan
Merged in a post:
Merge Fields for Templates
Josh Comer
I would love to have Merge Fields that would auto-populate data from ClickUp into different fields as in: task names, subtask names, and task descriptions.
I'm thinking of "merge fields" from my experience with Mailchimp in which I can write
|FNAME|
in an email, and Mailchimp automatically pulls the First Name of the email recipient and places it in that email.I would love to be able to have template tasks take on certain characteristics based on a merge tag used.
E.g. If I have 10 tasks called "Upload video to YouTube" that are set for different projects, it's easy to confuse the tasks. I think a merge tag system would be a fantastic time-saving tool to help rename items. I.e. a merge tag that lives in a template that changes the name of a task based on the name of the project.
Lily Chan
Merged in a post:
Dynamic Fields for Templates
Lesford “LJ” McKenzie
This would allow us to be able to build faster, if there could be dynamic updates made when you select a template. As in, if I have a folder template I would add in a [client name] place holder wherever I need dynamic info and then when I use the template it prompts me to fill in the needed dynamic fields. *Hope this makes sense. If not, let me know. P.S would either need a standard set of place holders we can use or 1 general one that would allow us to replace the placeholder with some text.
Lily Chan
Merged in a post:
Global variable pool
I
Igor Declercq
Being able to use global variables would be a huge improvement on templates.
The same principle as Postman for example where one could define a list of variables based on workspace / space / folder and then be able to use those inside templates (document / task / ...)
A prompt could be shown when using an "unknown" variable when applying the template. This way only 1 syntax can be used to use pre-defined as well as template-specific variables.
Load More
→