Make Task templates available to other projects (Task templates library)

Any update on this? Lacking this basic functionality is likely to move my team to a different platform.


No update on this sorry. The entire Asana adoption is tied to this specific feature? :scream: Did you check out my “task factory” concept as a workaround?

1 Like

Hi all,

FYI we’ve introduced a new “Add tasks…” rule action to Flowsana - it’s not exactly the same as task templates as it adds task(s) as the result of a rule trigger, not by user interaction; but it might be helpful in some use cases being discussed here.

Basically it’s just like the Flowsana “Add subtasks…” rule action except it lets you add one or more top-level tasks to a project (and those can have subtasks). Because those “template tasks” are created and stored in one separate project, you can reference those tasks in rules within any number of projects, so you only have one instance of the “template”, instead of having to keep and maintain task templates in each project.

This is a pretty essential feature. Has anyone yet confirmed if Asana have it n their roadmap?


Hi @Jon_Burdon and welcome to the forum,

Asana’s policy is not to publish a public roadmap or comment on future features, so we’ll just have to wait and see if it gets added at some point.

Hi @Michelle_Tenuta,

Yes, I understand. Asana has this issue as well at times, where its rules fire before one has finished typing the name of a task, for example. It seems both apps are a victim of our success, so to speak - rules are often firing faster now than before, which leads to that issue.

The easiest solution is to make a trigger other than “task newly created” or “form submission added” - would it work for you to trigger the rule on the setting of a custom field to a certain value or adding a tag to the task; or would that not work for your workflow process?

The only real way we have to solve it directly is to add a delay in firing certain rule actions, like that one; we’re really reluctant to add an artificial delay, but we are considering it…

I ran into a similar issue because I had an integration that created a Google Drive folder (via Zapier) when a task was created. However, because the task name was being typed as the integration fired, folder names were getting truncated.

I solved it by using another field as the “confirmation” of the task being ready. In my case it was a Custom Field called Status, in which the default value was set to “queued”. The rule was set to check for a new task being created and the Custom Field being set to “ready”, so the folder wouldn’t be created until after the task name was completely typed out, and the Status then changed to “ready”.

Just curious, how is that status change occurring? The user creating the task manually sets it once they’re done typing the task name?

@Phil_Seeman that’s correct, it does have to be set manually. We normally leave new tasks “queued” until the project starts (and is set to “ready”), so it’s a natural sequence. However, I can see it being an unnecessary extra step if one would always want to kick off the rule after typing the task name.

Yeah, that was my thought when I read your post. But as you say, it works out fine in the context of your particular workflow, so that’s good!

Just jumping on this bandwagon. Upvote, we need this feature!!

1 Like

This functionality is a determining factor in continuing with this software. With other options offering this option, we are considering a switch.

1 Like

A template created can only be used within one project and cannot be easily copied to another project.
There may be a scenario where multiple projects can use the same task template and in the current situation a template created in one project cannot be copied to another project easily. you will either have to create a task from the existing template in project A, add that to project B and convert that task to template or recreate the template in project B. Wouldn’t it be easier if you have a copy template option from one project to another?

Asana, please provide a native option to copy templates than work arounds!

1 Like

I am pretty sure there is an existing thread on the topic but I can’t seem to find it. Maybe @Rebecca_McGrath can help!

1 Like

Not sure if this has been suggested before - use RULES to create projects that says “When a task is put into THIS section then create the following subtask”. Then use that subtask to define the template and select the project where it should go (all within the rule).

No when you make a new project in that section a subtask is created that then becomes a main task in a different project. You can do this rule for every project!

Thanks for the suggestion. But my point here is more like an idea for a feature that can be implemented at the tool level. why do we have to complicate it so much when a simple feature can be provided. Like have an attribute for a template like global and private. global templates are available across projects while private template will be accessible only within a project or something.

It would be great to be able to house our task templates and existing forms in a library so that we can easily add them to new or existing projects without having to manually re-add the title, assignee, description, subtasks, etc… Having a feature where we could bulk-apply existing task templates or forms would be SO nice.

Right now, we use a lot of task templates to allow for people to easily write all the info someone needs in order to successfully complete their task. While this is great, we did this after already have a number of project boards and just recently added it to the project board template we use. Therefore, the existing projects (about 20 of them) do not have the individual task templates.

Same idea goes for forms, it would be great to be able to pull from some sort of library of all of our forms so that we can just add them with one click, rather than having to manually create a new form or task template in each existing project.

Also, although it’s great to be able to add the task templates to the templated board, it would be nice to be able to create a new board and just have the ability to add the task templates / forms that already exist in our organization.

1 Like

Hi @Courtney_Close

There is an existing topic and I have merged your request with it. Make sure to add your vote in!

1 Like

Task Templates are only half useful if they cannot be reused across projects and teams. Need company-wide templates to create consistency across all projects and portfolios and teams.

1 Like

just a head up for this feature request. i see a lot of traction on this and it is open since feb 21 which is two years ago (!) @Asana_Admin-IT can you pls share an update?