It would be really helpful to be able to manage more complicated work breakdown structures that require nested sub-tasks within nested sub-tasks. While Asana allows you to add nested sub-tasks they don’t appear in of the main views (list, timeline, gantt) unless you open the detail task view. This becomes very difficult to manage on larger technology projects where work needs to be broken down beyond 2 levels.
They do allow you to do it, for flexibility reasons, but from experience this is rarely a good idea. There are various ways to not nest subtasks.
You might benefit from my explanation here https://www.youtube.com/watch?v=qm9Zo10MTc0
Your product feedback is valid though
Hi Bastien. Appreciate the response. I watched your video and while I like the idea for something like managing a multitude of properties, I don’t think it holds up well when for technology projects in a client facing environment. My main goal is to breakdown work and manage dependencies in a way where when timelines are missed, we can easily reschedule the work and know what work needs to shift to address the delays. I don’t see how that can be done with the approach shared.
If you define dependencies between tasks, and use the date shifting date update in tasks, it should work.
Nesting subtasks is not a problem in its own, it is just harder to create dependencies between tasks when everything is hidden in subtasks…