I agree with the topic. It’s unbelievable that I have to add any subtask to project and this create a duplicate on the board. I have switched from another PM tool and I already paid but if I had known I would haven’t bought it.
4+ years after the creation of this VOTE and there is still no improvement? Come on Asana! You can do better! Having subtasks linked to their parents’ project should be easy for you guys! PLEAAAAASEEEE! And thank you.
I’m afraid that Asana has existing design decisions that mean a seemingly simple change to “home” Subtasks into the parent Task’s Project would cause downstream consequences that will break more views and workflows.
Example: The project Calendar and Timeline both display all Task entities in the given project. Subtasks are not displayed unless specifically homed there, themselves. If Calendar and Timeline stay the same and subtasks automatically join the parent Project, we will all suddenly find our Calendars and Timelines exploding with subtasks. Some of us will be moderately satisfied, some neutral, and I’m worried the majority will find this to be negative. Yes, Asana can fix this with one or more new switches, toggles, view selections etc. (“Show Subtasks on this Project? Y/N” and/or “Show Subtasks on this Task?”) Were I their architect, I would not choose to layer on more bandaids solely to make up for failure of previous bandaids. Asana needs a fundamental change in their approach as to how data is displayed and how that display is controlled, propagated, and shared. Views never should have been so rigidly Project based. Users should have been provided more flexible tools to design views that can include multiple Projects and parts of Projects based on criteria other than solely belonging to a given Project (or Team).
TLDR: It’s broken but isn’t easy to fix.
Agreed. I remember reading awhile back that they had devoted a team to working on the way their architecture handles subtasks—given that no headway has been made, I’m beginning to think it indeed a major architectural limitation resulting from the lack of foresight in the past.
Which is understandable, we can’t always think of everything…but idk, sometimes I wonder how obvious things get overlooked or released half baked (like markdown, task templates, nested portfolios, etc.).
Crazy to see that the request has been there since 2017, and so many people gave feedback and complained about it, and we are yet to see this feature in Asana…
2 posts were merged into an existing topic: Show project on subtask in ‘My tasks’ view
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.