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).