They’ve mentioned in the past that the relationship between subtasks and parent tasks is something they’re planning to tackle in the future (though it seems like they’ve been at it for a while), so I’m hoping that’s an indication that it’s not a case of them sticking to their initial design decision and more to do with the fact that it would be a major undertaking to completely overhaul the way their architecture works.
Hi @Bastien_Siebman, @Nicolas_Fischer and @Skyler! Thanks for sharing your feedback. We have explained this a couple of times in the Forum, but because of how subtasks were built in the first place, there is no easy way implement this change. Updating subtasks in Asana is technically a lot harder than what it looks like, and while we haven’t nailed it down yet, we’ve made some progress recently and these features were launched:
We are also working on implementing subtasks on Project Dashboards, stay tune for updates soon in our announcements category.
We continue to bring this up in most of our meetings with Product to make sure we keep this conversation open and continue to evaluate solutions for all features like Portfolio and Workload. We will post an update as soon as we have more one!
I guess my biggest question is: does Asana want to change the way subtasks behave (not belonging to the project) or do they just want to add some features here and there to make it easier for everyone to work with these constraints.
There is a lot of collaboration work within each team in our company and we don’t want to put every single small task as a task on each project to avoid a long overwhelming project interface. However, we want to calculate everyone’s workload in the portfolios including all the subtasks. I can’t find a better solution other than stop using subtasks to get an accurate number in the workload view. Can we update this feature?
Hi All, I agree this should be a standard feature but I have determined my own workaround that is working nicely for my team. This may have been discussed in earlier posts, so forgive me if I am repeating a known technique. Workaround as follows:
Establish a template task for your particular project using the customization feature located at the upper right toolbar of the asana display (just under your account image).
Create a subtask within the template task and go to the details section of the template subtask. Link this subtask with the project you are looking to populate in the workload view of the Portfolio feature Shortcut to evoke the project directory “TAB+P”. Click done.
Now that you have a template task and associated subtask with the established link to your desired project, the subtasks will show up under the portfolio workload view. However, there is one issue with another simple workaround. Each time the template task is used to create a new task, a new entry will appear in the list or board view sections. So, create a section that you will essentially hide to the bottom (if in list view) or to the far right (in board view) use to dump these so it will never occupy your display space. Then, go back to your template task to define the section in which you want this basically useless entry to live, but out of your view.
With these settings, as long as you start your new task with a template tasks that has these properties, you won’t have to do anything else manually.
You will now be able to see your workload views populate under the assigned individuals responsibilities. It’s far from perfect but it sort of gets the job done until ASANA releases an update with a more streamlined approach.
Justin_Poma I am a bit confused by your solution, but also intrigued. Basically any time you want to create a task in this project, you actually use the task template, and every time you want a subtask you use the one that has been provided? And the “trick” is that the subtask is already multi-homed so you save some time + make sure you don’t forget to multi-home it? What if you want multiple subtasks?
Can you set up a rule in your project templates that anytime a subtask is created it is added to the project? If so how would that look. As a project Manager manually adding every sub task to the project is a lot of overhead.
In a Template if I add all the subtasks to the “Template Project” when I create a “New Project” from that Template what project will the subtasks be associated with the “New Project” or the “Template Project”
I would like to add my voice to this potential feature as well, though I understand the solution is more complicated given how sub-tasks were originally created. We have two use cases in which subtasks are particularly useful:
I’m the project manager for an annual report and proposal that includes multiple (15+) articles and components (10+). Each article/component is a parent task with at least 3 or 4 subtasks documenting the actionable steps for that article/component.
In this particular case, adding the subtasks to the project is a time-consuming but generally manageable. I use a section at the bottom of the list “(subtasks)” to collect all the subtasks without cluttering the rest of the project.
My organization also has program/process management projects where a single task moves through the columns (board view). Subtasks are used within the request to assign and date the work. We use Rules to automatically create and assign subtasks when the task is moved through the process.
In this case, adding subtasks to the project requires more diligence and it’s much harder to manage since tasks (with auto-generated subtasks) are created in real-time and are based on its movement through the process and assigned to various individuals. I would love to know if anyone has some tips for this!
See snippet. Basically, in my organization set up an individual staff member may have multiple assignments that they are working on, or can be working on at any particular time. The catch is that this assignment may be part of a larger project or higher level assignment and it is nice to keep the tasks as a subtask of the main task. The issue is, Portfolio view can give a misleading representation of an individuals workload as it does not consider subtasks. There are work arounds but like any workaround, it isn’t ideal. Thought this could be helpful for my team and possibly others. Thank you for your attention!