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

[Spratt_Consulting]

I’m just confirming that even though we can add multiple projects to the task template, the task template still will not show up in those new projects?

[anon30083410]

Chiming in on this. The ability to apply the templates across tasks would make this really useful. Right now the way the task templates can only be used within a single project makes them redundant. I need to be able to apply them across projects. This would also really help if we ever have to update a template, instead of looking at updating the template in 10-15 different locations (which won’t happen, which is why we don’t use the task templates)

[Jose_Martinez]

We really need these Task Templates to be available in the Library like custom fields

Even better would be “Section Templates” and of course added to the Library.

I’ve been on a crusade to eliminate the use of Subtasks since Asana’s development team hates them so much (honestly, why are they even there? haha).

We want to use all these new features like Dashboard, Timelines, Portfolios, Status Updates etc…But none of those account for subtasks, they don’t even exists.

Then Task Templates come around and so far they drive you to use subtasks again…I’m so confused.

Conclusion:

1. • Task Templates available on Library, like Custom Fields
2. • Give us Section Templates, same as Task, but 1 level up. Also add them to Library

Thanks

[steph3]

So confusing: why is everything so siloed in Asana .

Rules–Great! Wait, you can’t share them, make them consistent across projects-so 10 new projects=10* X rules to recreate from scratch

Task Templates–Fantastic!!! Only you can’t really use templates across projects…Wait, what?

I understand the data model likely stands in the way, but why are so many productivity features completely hampered by the lack of scope and reach from a user standpoint. Do people only have no more than 5 similar projects they jump between?

What good is the (very useful) ability to convert a task to a project if none of the supporting workflows and automation translate to the new project?

[jeremyw]

@steph3 - I couldn’t have stated this any better! I do not understand the reasoning behind the siloed thinking. Come on Asana developers, you have to do better here. #BreakDownThoseWalls

[lpb]

@Martin12 and others here,

Until there’s a better way, perhaps this workaround will be attractive to some of you:

Why and when use task templates

@Michele_Giorgianni, This is a bit of a hack, but I tested it and it works. It will be useful if you have Asana Business or Enterprise until there is a more direct native feature in Asana, I feel. One time only: Make a project called Task Templates and add sections corresponding to each destination project where you’d like to use these common PM and other task templates Add one rule for each section with Trigger: Task added to section (this section) and Action: Move to another project (the d…

Larry

[Michele_Giorgianni]

Thansk Larry - it is bit of a hack and I don’t even really follow it. I’d like something everyone here can use, not just me…and for that, it has to be simple. I appreciate the response though! hopefully it will get added in as a feature.

[lpb]

@Michele_Giorgianni,

I understand, but recognize that this was intended for everyone’s use in your org who needs it (once set up, which is quick), not just one person’s.

I’d be happy to explain it more if unclear and you might want to use it.

There’s no public plan on Asana’s part to implement a task template library so I don’t imagine there will be another way to do this for a while.

Larry

[AliciaP]

I was thrilled to implement task templates across the organization and very disappointed across finding this post and discovering this wasn’t possible yet… here’s an easy workaround that worked for my use (only needing these templates in certain projects):

1. Create task template in project A
2. Add to project B → convert back to task
3. In project B, convert to task template
4. Remove task template from that project

[Steve_Day]

What is the timeline for templates to be available across the workspace. They are virtually useless without this functionality.

If I have to make multiple copies of a template which are not synchronised then it simply adds duplication which makes maintaining/updating them impossible.

Assigning a copy of our task template and moving it to the appropriate project is a simple solution that means your only have one version of the template. However, I just don’t see the point of the template feature.

Please sort this out ASAP

[anon34475399]

Seconding each and every person in this thread – for our business we run into this issue every time we need to set up a new project board (which is on a regular basis, as we work with multiple teams, multiple clients and multiple stakeholders, so we unfortunately can’t reuse project boards on a recurring basis.

Hoping for an update on this in the foreseeable future!

[anon44310414]

Hi all,

Is there a way to make Task templates available across all your Projects within the same team? Or even across different teams? Or do I have to create Templates over and over again in each Project that I want the task template to be available in?

Even when I drag the template to a different Project, I can’t see the template in the “Add New” drop down.

[Andrea_Mayer]

Hey @anon44310414 this is not currently available.

You can read about all features of task templates here: How to use task templates in Asana. • Asana Product Guide

As a workaround I suggest maybe creating one project that just contains just tasks that you use as templates. Then you would have to duplicate the tasks whenever needed.
Or duplicate into the relevant projects and then save as task template there also.

@Emily_Roman I think this could be moved to the product feedback category

[anon44310414]

Thanks for the reply @Andrea_Mayer . The problem with duplicating the task is that is automatically is marked as complete and with automated rules, they always end up in the Completed section. Not the end of the world, but just an annoyance when constantly having to duplicate. I’ll read the other forum post, thanks!

[Andrea_Mayer]

Hey @anon44310414
yeah this feature would definitely be useful for many Asana users (me included) so once that is moved to the Product Feedback category we can upvote it

[Bastien_Siebman]

I agree with @Andrea_Mayer , this is concept I called “task factories” for project templates, but that could apply to a single project with task templates in it

Templates can also be "task factories"

Hi , Following on the discussion with @LEGGO on Break long templates into stage-focused templates, it gave me the idea to share that concept of using templates as factories :factory:. Too often, users see a template as a way to create a project, and then they feel like they need to “stay” with the project. However, a template can be used to only “fabricate” tasks, and then you can move tasks elsewhere. A couple of examples: your client process takes a year, you create a template for …

[lpb]

@anon44310414, I provided a quite automated workaround for Business/Enterprise users, though all but the rules part could help others too:

Why and when use task templates

@Michele_Giorgianni, This is a bit of a hack, but I tested it and it works. It will be useful if you have Asana Business or Enterprise until there is a more direct native feature in Asana, I feel. One time only: Make a project called Task Templates and add sections corresponding to each destination project where you’d like to use these common PM and other task templates Add one rule for each section with Trigger: Task added to section (this section) and Action: Move to another project (the d…

And everyone here who wants to vote, please do so here:

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

The new task templates functionality is great, but what seriously limits (and likely eradicates) its usefulness is the fact that a Task template is only available in the Project it was created in. Our workspace contains different Teams each with many Projects. We currently have a ‘Tasks’ project in a central Team where users from all Teams can duplicate tasks and move them into a Project. So, the ability to access common Task templates in all Teams and Projects is essential for this to be useful…

@Community_Managers, Perhaps merge this thread with the above.

Thanks,

Larry

[Emily_Roman]

Thanks everyone! I’ve gone ahead and merged this thread with Make Task templates available to other projects (Task templates library)

[Megan_Rocko]

Echoing what many have already said. We really need the ability to create template and then apply that template to other projects, not just house the template in one project.

My use case is creating a template with various tasks that all waterfall with dependents, then apply that same flow to all projects I create.

Please consider this as a feature for your roadmap, you’d make a lot of uses very happy

[Marie]

@Andreas_Loftager

I love the new task templates, but when implementing them I had to copy/paste the original tasks I was using before LOADS of times. Because, when you convert it into a template, it then belongs to that project. And I use a template - with certain subtasks and collaborators - in a variety of projects.

Why not make any task template available for other projects than the ones they are created in? Add to library (just like with fields). Then you can add it quickly to X number of projects.

I would probably make it flexible too if you wanted to include the

• subtasks
• collaborators
• field values
  etc
  of the library task when you add it to a project.

So, I make a template, add Lisa and Max as collaborators, a description, and 10 subtasks. I fill out the fields.

Then I enter a different project, I click add task template, and I select an option called “add from library”. Then I search and find the template.

Then I select which items I want to keep from the library template - I select the 10 subtasks, the description, and then maybe I de-select collaborators, because in this project I want John and Anna to be the collaborators. The fields automatically are added depending on which fields are present in this other project.

I think there are many interesting benefits from something like this.

cc @Andreas_Loftager