Template assigned tasks show up in My Tasks automatically?

We would like to see this functionality implemented as well. Seems like there should be logic that if a task is assigned in a template then it does not show up in a user’s task list. Sure you can rearrange them to “hide” them but it would be nice if this was handled by the software vs various workarounds.

21 Likes

The functionality to suppress tasks that are assigned in a template from showing up in My Tasks needs to be added. Otherwise, you get team members marking template items as complete which messes up the template.

30 Likes

100% agree. Templates should be treated completely separate than projects.

A template is a project’s preset format that eliminates having to recreate it each time it’s used. There are no actionable tasks and shouldn’t be mixed in with project tasks.

30 Likes

Can a generic or department-specific user be created and associated with Template tasks? When we create templates, we don’t know exactly who will be assigned the task. We do know it will be someone in ‘Sales’ or ‘Operations’ or ‘Finance’. When the template is used to create an actual project, we would change the generic user assigned to actual users. Possible?

1 Like

@Carol_Dapogny – Not possible right now. But you could add a custom field drop down instead! You might name a custom field “Department” and add drop down labels like Sales, Operations, and Finance. Hope that helps!

For those who think template tasks should not show in My Tasks, make sure to upvote this thread!

26 Likes

I completely agree. This needs to be sorted out as soon as possible as it’s not logical for any tasks in templates to show up in a to-do list. It creates confusion and makes the entire flow ungainly and cluttered

5 Likes

I have just switched my team to using Asana and we are really utilising this feature of templates a lot.

Really surprised to see that template tasks appear in My Tasks - it makes no sense! Very confusing and not good for encouraging Asana use with a team new to it by having to hacks like hiding in Later. What if we want to utilise Later for what it’s intended for?

5 Likes

I just wanted to add to the chorus of voices who are saying that this functionality is necessary for templates to be useful to our team. I’ve upvoted the product feedback request as well.

Asana team, please hear this feedback and implement it into your product.

6 Likes

Yeah, this is crazy. I am in the process of setting up Asana and I have already broken templates I just created. Explaining to my team that a template shows up in tasks is just embarrassing. I was hoping this would be a good alternative to Jetpack Workflow but I am not so sure that is going to work.

4 Likes

Hi @Tom_Woolley,

What specific concerns do you have? We’d be happy to help you explore more ways that Asana can work for your team. Keep us posted :slight_smile:

What we’re getting at is that we don’t want the tasks that exist within a TEMPLATE to appear in people’s “My Tasks.” When the template gets used, of course the tasks should get assigned-- but it would be much clearer to the users if the tasks were not assigned just because they were part of a template.

6 Likes

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

5 Likes

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.

6 Likes

@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!

1 Like

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.

1 Like

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.

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

14 Likes

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?

  • Hard to explain, especially for new Asana adopters.
  • Sounds (and is) clunky to implement for the end user (user: “Why do ‘we’ need to do this when ‘you’ created this project template thing?”).
  • Easy to break. If a user completes or deletes any of the tasks in the project template, the template is now effectively ‘broken’.

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…

4 Likes

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:

  • In templates, we should be able to assign tasks
  • Those assigned tasks should not show up in My Tasks until the template has been turned into an active project.

Thank you so much.

5 Likes

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!

1 Like