By far the most frustrating aspect of Asana is the Subtasks association to Projects. People have been complaining about this for years and they still haven’t done anything about it.
Hi @asana team it seems crazy to me that Subtasks don’t inherit their Project. Has it really been 4+ years and no solution?
Starting to use Asana in late 2021 and very surprised this isn’t default behaviour. This feature was requested in 2017. Is there an ETA?
@Marie We are working on a project with more than 50 subtasks being created each day for a main task. I will list the painful experience with asana s current design :
New subtask won t get custom fields created in same project. (Until we add it to project)
New subtask doesn’t have automation rule based capabilities. (Until we add it to project) (At least if rule capability was there, we could automatically assign subtask to a project)
New subtask of subtask is still not visible in project task tree neither in list nor in board view. (Even if we add it to project)
99 % of the times, everyone would want subtask to be added to the same respective project or parent task and only 1% of the time OR ppl want it to be added to some other project. (Better to consider adding to project automatically so that project assignment can be changed whenever it s not needed). That makes life easier for 99% of ppl, 99% of time.
To summarise, the current subtask feature is like a Burger made in Mc Donalds & it’ employees yet don’t know wether to pack it in a McD box OR Kfc box yet. Imagine every minute the employee has to be reminded that Burger was made in Mc D only.
It s the same situation for us now. Every time we have to press that project button and add it to a project
@IvanStaykov Just to clarify, are you currently using Zapier so that when a new subtask is created, it automatically gets added to the parent task’s Project?
I’d accept this as a temporary solution for me although it’s not the best but at least it would get the job done. I was playing with Zapier but couldn’t see how to assign the Project to the subtask. Thanks!
I think it would be helpful for the Asana community to know what other features are being worked on as priority over this. Without that context, it seems insane that such a small feature request with so many passionate user complaints would have been ignored for over four years, especially when it seems like the only argument against it seems to be some “principal” about not “over-using subtasks” – like, that should be up to the users, shouldn’t it?
I’ve been a free user on and off for the past two years, and the fact that Asana can’t address this issue makes me resistant to upgrading to a paid plan.
When will this and overall treatment of subtasks to be like main tasks everwhere in Asana be fixed. This is a HUGE issues in effective use of the tool and causes massive frustration with all project teams. Please, please update on when subtrask handling will be evolved.
@Karen_Smart — It’s hard to tell. Asana doesn’t provide a public roadmap like other competitors. They sometimes resolve things in a few weeks while others are still open after 4+ years. They do a decent job at letting us know when they do finally fix something.
On a regular basis, Asana adds capabilities around subtasks. They have been added to the list view, then the search, then the reporting… I can say without giving details there are other things cooking on the roadmap…
@Skyler the Community knows you are frustrated with subtasks
I too have been praying for this for some time. Still hopeful. In the meantime, I am using Zapier across about 50 projects to find new subtasks and add them back to the parent task’s project. It is very cumbersome and not 100% reliable.
A solution may be to add a rule ( ideally for all accounts, not just Business and Enterprise). Subtask added in Project → Set Project and Section
This would solve the “parent tasks could be in multiple projects, so which project is it supposed to be added to” argument. It would be added wherever the rule was in place.
Love you <3
@Bastien_Siebman — It’s primarily the lack of communication and roadmap. Subtasks are second-class citizens in this ecosystem and maybe that’ll change at some point, but it’s just one piece of my frustration. That being said, Asana is not a customer-led company and that’s okay. Customers aren’t always right. There are other options out there and folks are free to explore those to find a better fit.
I do look forward to what Asana introduces in the future though and am glad they have such motivated champions like yourself to keep morale up and police things around here.
tl;dr FIX THIS
Please fix this design bug now.
The fact that there is no way to automatically add subtasks to the parent project is a very severe defect.
The reason it is a problem for all of us is that it makes all of the subtasks invisible to our boards. If subtasks were automatically included in the project they tasks could be used as epics and subtasks as stories.
The way it is no breaks Asana and makes JIRA a more attractive alternative for scrum or Kanban.
This is not a design bug, this is not the way subtasks were intended to be used even though it does feel like a bug, I agree.
Bug vs Feature is in the eye of the beholder. The utter un-usability of most US States’ unemployment benefits websites is a design feature in the eyes of some legislators, for example.
Hey, I work for Chessable, a company that works using Asana every day.
We would need to have this feature implemented to help our team members to easily track better which subtasks belong to one project or to another.
I attach a clear example of how much confusion can generate between tasks and subtasks.
In this example, the task Assets (Pub Manager) belongs to a purple project whereas the subtask “Blurb on course page” that belongs to this task doesn’t appear to be part of the same project. Does it mean that subtask doesn’t belong to the same project?
It would be really useful if these subtasks automatically appear to be part of the project.
Yes indeed, technically they don’t belong to the project and what you see is “expected” behavior and a know situation. You can add the subtask to the project, in a dedicated section for example, as a workaround. You can have a look at F2 and F3 on 🔥 Hottest feature requests and their workarounds
Hi @Bastien_Siebman - with the number of feature requests for this (my creative agency included, Haddad & Partners) it would be ideal to see subtasks associated with the project. I understand that was Asana’s original intention but it’s confusing for users (for example: when a team member is looking at their my tasks they see a mix of tasks and subtasks in that list - the tasks have the project listed in the projects column while the subtasks do not list the project it’s a part of so it takes more effort to see where that subtask came from). It’s really not ideal to have to do a workaround for this. Our development team at the agency is in the process of migrating from MS Planner (and BugHerd) to Asana but this has been a pain point for us (and to others clearly). Ideally even being able to have that as a setting (allowing us to opt in to automatically have subtasks associated with their projects) would be really help. Is this being considered at all?
Hi Asana, You’ve done a fine job with the software overall, however I am finding it difficult to get my fellow team members within my organisation to love it, as the confusion around ‘My Tasks and subtasks not appearing within projects that they are already linked to’ keeps rearing its ugly head. Please sort out this crucial part of ones individual management of their assigned tasks & subtasks. This seems to be a long term issue, and it would be great to hear from Asana in terms of at least identifying that its an issue that is being looked at. Thanks, Andy
Is 2022 looking like a good time to have this. Everyone need this. Pls hear out. Anybody in asana software development hearing us ?
Have u guys in asana internal team ever tried to add subtasks to projects urself. I bet u will feel the pain of it.
Even our most bored employees in the team don’t want to do this everytime.