2.5 years later and this still hasnāt been addressed? This is beyond frustrating/disappointing. PLEASE tell me this is being worked on!?
This 2.5 year old threadā¦ any chance that we can get an update here?
If youāre not going to make this change and it is not on the road map, please just tell us.
Thank you.
Asana never says whatās on the roadmap, so you should consider it wonāt be around before a while.
The work around Iām going to use is to mark all tasks in a template as complete, and then when I use it to create a project, flip all tasks to incomplete.
Hopefully Asana fixes this soon.
Nice trick
is this bug fixed now?
my collegues very often set those tasks to ādoneā , but they may stay āundoneā in the templates!
very confusing. and annoying, that causes erros in workflow.
assigned tasks in templates may not be shown in task lists.
We also struggle with this. We have numerous templates and a lot of us are assigned to the tasks within those templates. Itās fine to move the tasks to ālaterā and then collapse as a workaround, but for someone like me who delegates a lot and is bouncing around from assignee to assignee, they āun-collapseā every time I go back. It only makes sense to not show up on someones list until the task is actually created. Asana please fix this so I can get my sanity back! My list is out of control and Iāve desensitized myself so much to the items on my list, itās almost pointless to even have a to-do list! Completely defeats the purpose.
My team absolutely hates having to see template tasks in My Tasks. They get in the way and people mark them as complete on accident, messing up the template.
Why canāt the Asana just treat template projects and task as different from normal ones? It seems silly that users have been asking for this for over two years and the only thing approaching a solution is āBanish it to Laterā
I see one particular use case that would be broken by your suggestion: the creation template phase, when you want to assign tasks to people so they can work on preparing it for the template.
My team uses template projects extensively. Weāll each be assigned multiple tasks in multiple template projects. We all now have an ever-growing mass of these tasks in our My Tasks that canāt be gotten rid of, only banished to āLaterā.
Iād like to see a feature where tasks assigned within template projects simply not appear in My Tasks.
There is already a gargantuan thread on this - I suggest mods merge this there to avoid diluting votes.
Can you link that? I can delete this and add my vote there
Iāve merged your post with the thread Stephanie has outlined. If you havenāt yet I would suggest you to upvote it!
Thank you @Stephanie_Oberg for your help!
Make it so custom templates donāt automatically share new projects with original template creator. Maybe make it an option when setting up the new project instead.
When a custom template is used for a new project by another team member, the original creator of the template isnāt necessarily working on the new project. Therefore, they donāt need to be notified every time their template is used.
Hi @Danielle_Kosh and welcome to the Forum!
Thanks for sharing your feedback with us! This is a popular request in the Forum and we already have a thread on this topic, so Iāve merged your post and your vote with our existing conversation to consolidate feedback on this topic! Iāll make sure to update this thread as soon as I have an update!
Thank you.
This is a huge oversight from the Asana team. There is zero logical reason to have assignees have tasks in their My Tasks for a project template unless it is just to piss them off.
Very poor form.
It actually makes sense during the template building phase, where you can assign task to people so they can prepare the task
That is what scoping meetings are for. And if you donāt have scoping meetings, then a single task outside the template to reference would be much cleaner than having a ton of tasks assigned and schedule (if you schedule within your templates which you should) to people who canāt work on anything.