When creating a new task from a task template, would anyone else find it helpful to be able to put variables in the task and subtask? I find that these repeatable templates have a customer or location that they are applicable to. If the name could include something like %location% then when created, a pop up window would ask for the location, and then it would substitute all the %location% in the tasks and subtasks with whatever was entered. Right now I need to remember to edit manually the main task and subtasks with the specific information.
@Jason_Fujinaka, I’ve moved your post into a new category where you can click the title to scroll to the top and vote by clicking the purple Vote button, as I just did.
Thanks,
Larry
2 Likes
Adding onto this, we would love this feature!
Our usecase would be; we have task templates outlining announcements we do and subtasks that feather out to respective projects for social / CRM / web etc… Would love to automate ‘task name’ variable in all subtasks generated and added to those other projects. Ideally when referencing the respective projects i.e. social media calendar you’d read ‘social post [task name]’ instead of just social post.
1 Like
Is this is a duplicate of Variables for project templates?
@Ragu_Kantamaneni, they’re similar, but different!
This topic is about the Task Templates feature and the other topic is about the Project Templates feature.
Thanks,
Larry
Thank, I realized that right after I posted it. 
I deleted the previous comment that I guess it didn’t work.
1 Like
I totally share this need.
1 Like
3 posts were merged into an existing topic: Variables for project templates
We need the ability to use variables (e.g., project name, custom field values, assignee, due date) directly inside task templates for both the task name and the description.
Right now, we’re forced to use rules to dynamically populate this info — but that approach cost us 10–15 hours of discussion and build time just to create a workaround. Even after all that, the rule doesn’t consistently run when all conditions are met.
If variables were supported natively inside task templates, we could:
-
Skip unreliable rule-based workarounds
-
Save hours of build/debug time
-
Ensure consistency and accuracy for dynamically created tasks
This would make templating much more powerful and reduce friction for anyone building automated workflows at scale.
@Chaya_Cloward I’ve merged your post to an existing one about the same topic. You can upvote the idea here at the top of the page, just like I did now! Thanks for sharing the idea.
1 Like