Youāre good @Bastien_Siebman, Iām trying to think of other ideas, but it seems youāve already identified them all 
You can also create milestone template, though.
2 Likes
Hi @Bastien_Siebman this must be done inside a project? I manage all my personal tasks with no project attached so I couldnāt use tasks templates is it ?
This is excellent! For the past few months Iāve been trying to figure out the best way to quickly create tasks for standardized requests, and this fits the bill to a T.
THAT is very interest. I threw in the towel on Project templates becasue it creates a disaster of double counted tasks. So no such issue with Task Templates??? Iāll have to give it a try.
1 Like
Yes at the moment task templates live within projects. In your case, the trick would be to adapt my concept of task factories and have a project only dedicated to holding those templates.
I am hoping project templates would soon hide tasks from My Tasks, but I donāt have any inside intel. In the mean time, look at F4 on š„ Hottest feature requests and their workarounds
Thanks @Marquis_Murray
@Bastien_Siebman - Love your insights. The reason why task templates work beautifully is that not everything in your business is BRAND NEW, so creating task templates is perfect for repeatable processes.
1 Like
Here is my list of task templates
- Blog Post
- Press Release
- White Paper
- Data Sheet
- New web page
- DG Email
Here is what would make task templates perfect
- ability to preset dependencies and pick a targeted start or end date
2 Likes
Do you know if thereās a way to use task templates in a project other than the project that you created the templates in? My use case is I have template projects for different types of projects, but some tasks are common throughout all those projects (i.e., Project Management tasks). Iād like to easily bring over just the PM task templates into the other project templates.
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 destination project, and optionally section there)
Add all your common task templates to this project, and continue to add one whenever you think of it.
To instantiate any one of these common task templates in any destination project, just add a task from the chosen task template in this project in the corresponding destination projectās section. Upon addition, the rule āattachedā to that section will re-home the task to the destination project.
Hope that works for you,
Larry
1 Like
Thatās a great Solution/Workaround Larryā¦
Just to confirm you would need a Business Subscription for that to work wouldnāt you?
Regards
Jasonā¦
1 Like
Great one indeed!
1 Like
Being able to add a re-occurring task (and its subtasks) to a project can be a real time saver.
This work around is pretty slick and certainly appreciated, but I would love to see a simpler āadd templated taskā function available to any project sections. It definitely works well when the task-template has been built in the project itself, but we need that next step.
1 Like
I am new to Asana, so apologies if the question sounds basic. I am trying to use task templates to create different types of tasks, which in turn would leverage different fields. Current use case is to develop a āblocker trackerā for use in managing issues in a project. I want the participants to be able to easily submit a blocker by providing a minimal amount of data. I see that I can add custom fields when I create a template, but I donāt see the ability to delete existing fields. For example, for the blocker template, I want to eliminate Dependencies and Description, but canāt figure out how???
A task template always shows the fields any task from the project would show. Removing a field from the task template means removing the field from the entire project.
Also fields like āDependenciesā and āDescriptionā are native fields on each tasks, you canāt remove them.
Does that help clarify things?
It doesā¦but it means that I canāt create custom templates for different task types. I am trying to create a very easy user experience where they only see relevant fields for the task type that they are assigned. If someone has a standard deliverable task, then more data fields are relevant. However, if someone has to solve a blocker task, then there are only about 4 fields that are relevant. Does this make sense? I want to only display what is relevant. Is it possible to front-end with a slimmed down form for these users?
The only way to get on-demand fields in a task template is to have the task template associated with a project that has only those fields. So basically you would have to create various projects, and people would have to go there to use templates, and then move tasks within the desired projectā¦
Hello Larry,
It seems that you shared a good idea for this issue, but my bad that I donāt fully understand the steps to take, it will be very generous of you if you can explain more in detail for nonexpert people like me.
Thanks in advance.