And it’s been in the product for over 2 years now with numerous people reporting it and no action / silence.
Like bas, and for the same reasons as he lists so reasonably, I’m amazed that a bug like this has been outstanding for over 2 years.
When? If this feature is not possible tell us. Please Asana, don’t let your community of users in the dark without answer, or a give a time-frame at least (next week, next month, next century…). More and more frustrated by the lack of answer on several basic features (UX common sense) in Asana.
So…How many votes does it take before a ‘suggestion’ is implemented? Enabling this feature should not even be a question. As asked by others, why would a subtask NOT inherit the parent project? At least set this as the auto-default and allow the user to change if they had some reason to. Since any task/subtask can be added to multiple projects, I don’t see any downside to enabling this feature!
Can someone at Asana please reply!?!?
So, I sort of found a work around for this that works for me and my team. If I wanted a subtask to show up on the same line as a task, I would have just made it a task to begin with…but I can’t stand subtasks not being assigned to a project. My answer: In each project, I created a Section at the bottom named “Subtasks”. All the unassigned subtasks then get assigned to the correct project and thrown into the Subtask section. This effectively solves with “no project” subtasks without messing up the rest of the structure I created. This allows me to easily see which project the subtask is assigned in “My Task” and in the Calendar view, and I just treat the entire Subtask section at the bottom like the junk drawer. Is it perfect? No. Does it work for me? Yup.
Hello @Afton_Boles. Can you please run through the steps on this again? I’m having trouble duplicating your results. Thanks!
Hi @Hoge ,
First step is to go to your project and add a Section labeled “Subtasks” at the bottom. This should always be the last section at the very bottom. Then, when you make a subtask under any of your parent tasks, assign it to the project and put it under the section “Subtasks” you just created. It will automatically try to assign these in the “Uncategorized” Section which appears at the top of the project or the Section the parent task belongs to, which kind of defeats of the purpose. If I wanted it to show in either of these areas, it would simply be it’s own task. Assigning it to the Subtasks section you created instead puts it out of the way and allows you to access the Subtask through the parent task like you intended. Because subtasks are not automatically assigned to a project, you have to assign them manually each time you create one. If you already have a bunch of subtasks that show up in your “My Task” view as “No Project”, you can highlight a group of them from this screen and assign them all at the same time if they all belong to the same project. This only applies to the subtasks assigned to you, though. If you need further instructions on how to assign Subtasks to a project, visit the Asana help page for subtasks as it provides very clear instructions. Once you have assigned a subtask to the project and under the Subtasks section, you can still access the subtask through the parent task AND it will also show under the Subtask section. If you mark one complete, it will also mark the other. I put the Subtask section at the very bottom and minimize it because they are basically duplicates, but it fixes the problem of “no project” in the “my tasks” and calendar views. Doing all of this allows you to assign subtasks (and subtasks of subtasks) to your project without them clogging up your parent task list or messing up the structure you have built. Hope that helps!
OK I got it now. Thanks the help! Have you tried setting up this hierarchy in a template project? Whenever I try to, it creates two copies of each subtask (one that’s correctly assigned to the project and one that’s unassigned) in the new project.
I really think if you make all subtasks part of its parent project (without actually adding them to the tasklist), that would solve a lot of current issues that are going on with the Timeline, Calendar, and even Boards. The subtasks should always reflect the project their parent belongs to, and you can probably come up with another function to determine if the subtask actually shows up in the task list with the parent projects. You can call it “show at parent level” or just “parent level view” something like that.
But for the most part, I would think most of us don’t want to see the subtasks at the parent level, but we do want to see them show up on timelines, calendars, and maybe even boards, though I could see the board requiring some kind of action, like a “show subtasks” or toggle, or something.
Thank you for sharing your feedback with us @Francesco_Alessi
This is a very popular request in the Forum so I’ve gone ahead and merged your post with the main thread we have to centralize feedback. I hope it’s OK!
Have a great Tuesday Francesco!
I stumbled across this issue because I was confused why subtasks won’t group under their parent task’s project in the Later section of My Tasks. I know why now. Annoying! Hope this is fixed soon.
Coming close to this requests 3rd birthday! Can you guys get rid of this headache? Pretty please?
Why wouldn’t you? If a sub-task belongs to a task that in Project A, it stands to reason that the SUb-Task also belongs to Project A. Otherwise, what’s the point of Projects? Or Sub-Tasks?
I can see many reasons. If a subtask is just smaller pieces of the same tasks, you don’t want them to count in Workload. You also don’t want them to clutter the calendar. And many people don’t want them to have the custom fields of the project.
It’s a pretty large investment for my team so that I can access Portfolio and its almost worthless to me without subtask being automatically added. The Work Around Is messy and adds extra task all over our boards that do not need to be there.
I completely agree. It’s critical. Asana needs to fix subtasks before rolling out more nice-to-have features.
Bizarre that this has been open for so long…please fix this it would be of immense benefit.