Hello,
Mee too, I would even say that it is mandatory for a template that its tasks do not appear in anyones tasklist.
The template is the model, the project is the instance of that model.
Please fix asap.
Marco
Hello,
Mee too, I would even say that it is mandatory for a template that its tasks do not appear in anyones tasklist.
The template is the model, the project is the instance of that model.
Please fix asap.
Marco
I would love it if template tasks were excluded from âMy Tasksâ, a template is not an active project, and this creates confusion across my team.
@Angie_Gilbert, @Marco1, @Colleen_Pickford - I hear ya. What I do is simply move template tasks into the Later section of my My Tasks. That way they can stay assigned to me, but theyâre filed away in storage. I use Later for things that I wonât action but I do want to reference and tasks that are assigned to me that donât have a due date or action item (such as template tasks). I hope that helps!
Iâm going to add my vote to fixing this. When youâre trying to get a bunch of office workers to adopt a new product that theyâre unfamiliar with, telling them to move their template-assigned task to the âLaterâ section isnât a good option.
I see a bit of confusion, possibly caused by the use of the ambiguous term âtemplate taskâ. Let me see if I can clarify.
To be clear about what people are asking for, we all agree that once a template (letâs call it âMarketing Kickoff Templateâ) is used to create a new project (say, âPandaâ), we want all the tasks in Panda to behave exactly the same as any other task - i.e. show up in My Tasks for each assignee, etc.
However, NOBODY wants to see the as yet-unactivated tasks resident IN a template to appear anywhere. A template and a project should have 2 different behaviors. Projects (and included tasks) are live; templates should not be. Templates and their defined tasks should stay waiting in the wings, behind the scenes. The process of creating a project from a template should be the magic wand that activates the tasks in that project.
Furthermore, template creators may or may NOT want to be added as, and notified as, collaborators on every task in every project spawned from every template they have created. In general, I would NOT want thisâŠit dilutes the meaning of the term âcollaboratorâ, especially if I create really useful templates and deploy them for a large org. Yet this addition and non-stop notification now occurs automatically.
Yet Asana currently provides no different behavior. A âtemplateâ is just another project that happens to (maybe) have the name âTemplateâ. I want to keep my âMarketing Kickoff Templateâ inactive. Thatâs why I made it a template (instead of just copying a live project).
Heartily agree with everyone on this post and have upvoted Todd Cavanaughâs related post. I appreciate the idea from Asana Alexis and a couple others about the band-aid of asking staff to âjust move tasks from the template to Laterâ, but as many have already pointed out, that is a weak solution at best. Why?
Iâm not saying anything that others havenât, Iâm just stating it again so it is crystal clear what this issue is and that âmove to Laterâ is a weak workaround. So weak in fact, that it prohibits me from implementing what could be a very powerful feature of Asana, a feature that our managers are actually looking for⊠âis there any way that we could pre-load these more complicated, yet recurring project types?â.
WellâŠ
Alexis, while I appreciate the suggestions to make this temporarily manageable, please understand that this is only a workaround and not a solution. Can you please confirm that our request has been forwarded to Development for consideration?
To clarify:
Thank you so much.
Hi @Christina_Dunn_Singh - We appreciate your and the groupâs feedback here. This thread has been moved to the #productfeedback thread here in the Community and the request is being taken into consideration. Thanks!
Work aroundâs are not a solution. Pretty sure in all software programs the term âtemplateâ is just that. Somewhere to start a project from but not an actual project itself. The template tool was the main reason we upgraded but after loosing hours of work cleaning up duplicated tasks we have abandoned them and like Asana a little less. I really see no benefit in Asanaâs version of a template.
The hack sort of defeats the purpose of having a template. The âtemplateâ functionality doesnât seem to do anything that couldnât be done by saving a project with the name âTemplateâ, which we used to do. I was very excited to see Template functionality added as I (wrongfully) assumed this was just the problem it was intended to solve! I canât tell that there is any difference between a template and a project.
Please do consider it. A template is only useful if, as @Antony_OBrien and @Jan_Hanson mentioned, it does something different than just copying an older project. The word âtemplateâ should involve âbeing ready to be used to create tasks but not actually existing as tasks to be done until you use itâ, otherwise it is not a template, it is just a project you leave there to be copied when you need. Having everlasting incomplete tasks on âmy tasksâ, even if they are collapsed, defeat the purpose. Project templates are important, we need them, but this problem does not let us use them.
Hello there, is there any update on this issue? I have same problem and now i want to create some templates, but i have same issue.
Thanks.
The workaround of moving âtemplate tasksâ to âlaterâ to avoid the problem of people having My Tasks cluttered with non-tasks from templates doesnât work well for us because
A year later and still not being addressed or acknowledged. Disappointing.
Agreed Daniel - we use templates extensively and having them clutter our tasks makes Asana difficult. Weâre using duct tape solutions to get around it.
Has there been any update on this? Iâm trying to advocate for using Asana exclusively; however, being assigned a templated task in our my tasks before they are real actionable items makes the template feature completely useless to us. What update can you give us?
Im using Instagantt to create timelines on templates in my account. The templates show in the project list as well. With that said, since the template has preassigned people attached to certain tasks, the template timeline and responsibilities show up in the âdaily task listâ even tho they are for a template, and not a real project.
Is there a way to omit template timelines from Task view?
Hi,
This is something people have been complaining a lot in the community. @Marie will be able to merge your thread with the existing one so you can vote on it!
Bastien
Thanks @Bastien_Siebman! @Greg_George we already have a thread on this topic, so Iâve gone ahead and merged your post with Project Template assigned tasks show up in My Tasks automatically. Feel free to had your vote at the top of this main thread!
Where is the âLaterâ section you all speak of?
The only collapsible section I have in My Tasks is âNew Tasksâ
DangâŠreally disappointed. I was really loving Asana until this was discovered. I just moved to Asana from Teamwork and I used Teamworks templates a TON.
Just reiterating to the dev teamâŠplease make templates not live!