As @Bastien_Siebman mentioned, subtasks do not inherit the project from their parent tasks right now. You can only affiliate subtasks with projects by manually adding the project to them. Once you add the subtasks to the project, they will appear in the Workload. Please find how to do it in this article.
You can certainly see subtasks in Workload, simply add the subtasks to the project and they will appear. You can do this by going into the subtask details and using Tab+P to focus on the project field or by going to the upper right drop-down and selecting “Add to Project.”
I hope this helps! Let me know if you have more questions.
Would love to see subtasks in Workloads too. I’m trying to get more of our departments on Asana, but it’s hard for me to sell it (and the upgrade to Business) if we can’t view resource allocation at that level.
I have been working with subtasks and workloads a bit. What I did is create a separate project & portfolio called “all working subtasks” which everyone’s subtasks get added into. Currently I have to do this manually, but I am hopeful that there will be a way to auto-update via the new rules functionality some day. By adding the subtasks to this project I am able to see the workload in portfolios as desired above. This has worked for us for now!
@Emily_Roman any news on this update? I have voted in the thread linked and it seems like this has been an ongoing problem for several years with no action on Asana’s side to address. This is severely limited the efficiency of my team and has rendered workloads (a function that I would like to take advantage of) as essentially useless.
(And yes, I know that I can add all subtasks to my project, but what is the point of having subtasks if that is the fix? It makes projects messy and inefficient)
Hi @Emily_Roman, following up on @Emily_August’s comment above in this thread here. We would really love to know whether Asana has plans to remedy this without the user having to add Subtasks to a Project.
For context: We have a small Brand Design team with many projects across multiple teams within a company (R&D, HR, Marketing, Sales, etc.) In order to better organize our work, we have projects named for each of those teams, and have demoted projects for those teams to tasks, with the actionable tasks for the project then demoted to subtasks. In order to maintain this level of organization, we’d like to keep those tasks as subtasks, rather than adding them back to the project where they re-populate as tasks.
Please let us know if there’s a fix in the works, thanks so much!
I think this linked feature is more complicated or misleading as a solution. Ideally, the feature would give the ability to measure the budget of subtasks in workload without the necessity/messiness of adding it at the project level? Thanks Emily!
Just adding to this thread as our example is similar and this lack of a feature is pretty crippling to the usability of workloads for us (and I’m sure others). We have Estimated Time as a custom field which allows us to make decisions around task assignment/project expectations. There are tasks that have subtasks with different team members assigned to each. Not having these “parent” tasks or the “child” subtasks show up in workloads is not only frustrating - but it overall useless.
Is there a plan to make this feature: “Show All Assigned tasks/subtasks” in workload? If this is just a request and not a part of the road map here? It would be helpful to know as we would need to find another solution to displaying/calculating actual bandwidth in our organization. Thank you.
I just wanted to add my voice in support of some solution here. Our teams have top level tasks in projects, but assign cross-functional work in sub-tasks. Would love to be able to optionally use-sub tasks in the portfolio workload view, without separately adding them all to the parent project. Thanks!