PLEASE DO THIS ONE!
This feature would make Asana way more efficient!
I agree with the thread…is this ever going to be implemented? Or, am I missing this functionality if it already is there?
I know this is being being addressed on Asana’s side of things, but I still wanted to echo this issue as well. I used the Tab-P method to have subtasks have projects added to them. Currently we have some Projects that have a separate section titled SUBTASKS where we can nest the subtasks after it is added to the Project using the Tab+P method. It works but it would be great if there was a more streamlined method. There are too many steps and my team does not like it.
It is kind of a pain to have to create the Subtask under a Task that is already assigned a Project, use Tab+P to add the Subtask to the Project, and finally nest the Subtask (which is somehow duplicated into the Project home) back into the SUBTASK section. This is the only way I have found to get our custom field of “Task Hrs” to show in the project portfolio.
Is there a way Asana can add a script for when Subtasks are created? The script could be triggered when a subtask is created under a project task, and the user could enter a default setting (for example; assign task parent project to subtask, add duplicated subtask to a hidden Section, some process that is automated?) Maybe this is a user setting that can toggled on and off for those who don’t want to use this?
I’ll let Asana answer, but in the mean time you can create such a script yourself, something that runs nightly and adds subtasks to the project under a specific section. Let me know if you need help.
I would be interested to learn how you do this! We use subtasks a lot in our work and it is very frustrating we can’t sort by subtask
I did not yet, but it would be nodeJS script ran by a scheduler. Contact me in DM if you need my help.
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.).