Come on Asana! This thread has been going on for years!
Multi homing is so messy! It just duplicates the task into the project. People put these as subtasks for a reason.
Having the entirety of the project in workload (including subtasks!) makes much more sense for proper visibility over actual workload.
We have a workaround project for task management too because the portfolio feature only works for high level viewing - it doesn’t help team leaders have an overview of details.
We use subtasks other wise there would be too many tasks in a project to manage!
This is the kind of thing that makes Asana completely unusable for me. It’s an absolute waste of time to have to fiddle with individual subtasks to get them to appear on the calendar other views. This is basic stuff, y’all.
I did this for my subtasks and it created another task for each of them in the project as a parent task in a new untitled section.
How is there still not a solution for this? I think this is a standard feature in other products.
That’s because a subtask that gets added to a project becomes a task in that project.
It’s weird and unintuitive compared to what we see with other task management solutions, but that’s what we’re stuck with currently.
Just to piggyback on @Skyler’s reply above, it’s not another task - it is the same task, just displaying twice. That’s important because if you make changes to it in one of its places, it will change in the other place.
Also checking in on a solution here, we configured our templates to be more easily focused on the higher level tasks but each step of our implementation task can be filled with 1-12 subtasks to fully complete and move forward.
@Bastien_Siebman The pre-multihome of a subtask only seems to work with an existing project but we would need this to be dynamic and tied to the project being created from the template. Do you have a suggestion to resolve this?
@Cassie_Bever I do not. Those 12 subtasks, are they just a checklist the assignee need, or you assign them to different people with different dates?
I agree. A subtask of a maintask belongs to that project you are working on. This is really frustrating.
Voting with my comment as well as my vote, ignoring the other issues presented above, this means my “My Tasks” is cluttered with subtasks with no context. I just have “approve paperwork” written 8 times but not one for each of the various paperwork tasks that we have multiple people working to finish. If I could sort by project I could grab the paperwork on my desk, approve it, and mark complete. But instead I have to navigate through every project to get the context of any subtasks assigned to me.
That’s a bit of an exaggeration isn’t it? Simply opening the subtask on the right will show at the top the parent task and the project…
Also, voting for this, as duplicating every subtask and converting them to a task defeats the entire purpose of a subtask. My team needs to be able to assign a subtask to other team members and add the estimated time and date for the Workload to even be a viable option for us to forecast and plan our loading.
yep, this completely eliminates the utility of my task list for us. Please assign a subtask to a project or at the very least, show the parent task and project somewhere in the my tasks list!!!
The parent task, if there is one, should show up next to the name of your task in the MyTask view.
I too would like the Project would show up as well—similar to other tools like ClickUp.
If you consider the overhead caused by an extra click on 8 different entries an “exaggeration”, why are you in the business of productivity optimization?
Just accept that many of us need subtasks to be associated to their parent tasks already
fyi I don’t work for Asana. And a long time ago I decided to spend my energy trying to find workarounds to help the community. Believe me: if subtasks were updated, I would save a ton of time because I wouldn’t have to help so many clients with issues related to subtasks…
We are talking about 1 click per task you have to do, and doing the actual work usually means several seconds of minutes of work. So I would stand by the fact that this extra click is really really small compared to the work each task usually represent. But see above: it would make my life easier it we didn’t need this discussion (and the other hundreds I had about the same topic).
On a daily basis I see most people not using Inbox zero for example, so they usually waste hours of work by not applying basic productivity recommendation, so I don’t think the extra second saved will have a big impact…
We want subtasks to be associated to their parent tasks !! Make it an option, you will not use it, I will.
Sooo… still no progress on this very annoying and frustrating topic? Where do we talk to the developers at Asana to get this resolved?
Developers don’t decide on features, the Product team does, and they are well aware of this topic which has been discussed for as long as I can remember.
Yes, they certainly are. But this begs the question: why haven’t they listened?
That’s a rhetorical question, and I’m aware that roadmap decisions involve a lot of context and nuance we’re not privy to at all. But it’s pretty frustrating to be one of the literally thousands of users screaming into the void about it to no avail.
I was recently engaged to help a moderately-sized organization evaluate and decide on a work management platform to adopt. And truly, if it wasn’t for this weird subtask behavior, they would have gone with Asana. They didn’t.