Indeed one way to get rid of subtasks is to promote all subtasks to tasks and use dependencies, actively blocking the main task until all the “steps” are done. Using a milestone (rather than a regular task) does not bring much to the table.
+1 Here. Really need this!
We use task templates and the template changes often and I’ve missed completing new subtask steps because I don’t see them by default!
Hello. Has there been any updates to this? Is there now a way to default with subtasks unfolded? If not, is there a projected date for this to be added? Thank you.
No update yet, Marie will update this thread if anything changes.
I never thought of this. I’m going to give it a try. Thanks Bastien.
Still waiting for this basic function !!
Hi @Richard_Turberville, welcome to the Community! Thanks for expressing your interest. If you’ve not already done so, don’t forget to vote for this enhancement at the top of this thread.
Hello!
I like the list view and seeing my subtasks pulled down within that view. But when I go to a different board and then return to a previous one, the arrow collapses my subtasks and I have to pull them down again. This doesn’t feel efficient at all and is frustrating. Is there a way to customize it to freeze them? I’d prefer to see them in one view on the list vs having to click on each one to have the side bar open on the right.
Thank you in advance!
Jess
Welcome, @Jess_Koehler,
I’ve merged your post into an existing request and you can vote for this feature by clicking on the title (or scrolling to the top) and using the purple Vote button.
Thanks,
Larry
Oh dear. Reading all of these comments over the YEARS has me realizing this is NOT being prioritized as a basic function. I’m in a trial to upgrade and I’m thinking that won’t be happening. Bummmmmmmerrrrrrr.
I started using Asana, because my coleague said he has experience with it and I decided to give it a go, but not having the subtasks visible is such a huge issue!
Overall I found most functionalities that I would need in my day-to-day, but this is an issue for me.
@Emanuil_Georgiev if you are just starting out with Asana, now is a good time to not start “bad” habits: don’t use subtasks when you can avoid them. In many cases, people tend to create a big tasks with lots of subtasks, when they could have created a section or even a project!
I’m trying to use ASANA for Sales type projects/opportunities and their respective tasks.
I’ll have anywhere between 30 and 60 active Projects or Sections. And I don’t see how that will work effectively.
I can share our own example to illustrate. We have 400 clients and 3000 leads.
A lead is a task, on which we place subtasks for meetings and quotes. As soon as a lead signs and becomes a client, we also create a project, and place the task in the project.
It means we have 3400 tasks (leads + clients) and 400 projects. Out of those 400 projects, about half are active. And that works great.
A common practice is to only use tasks and place subtasks on them, and I believe that’s a mistake. Having 400 projects is not at all an issue, especially if you also have the 400 tasks that goes with it because it gives flexibility and various access points.
Hi,
I see your point, creating Projects only for the Clients makes sense as they will be fewer. But if I can manage the sales process with just tasks and sub tasks, I can also do it for delivery, as it’s often simpler than the sales.
And from what I see, in order to have a good overview of the Projects one needs to use the Portfolio functionality, which is in an “expensive” subscription tier.
I’m currently just exploring Asana and I don’t know if my company will agree to pay for any subscription tier, so
I’m either going to use the free tier or the 10,99 out of my own pocket, so I can keep my sanity till the company decides what tool they are going to use other than MS excel …
It helps, but if for any project you also have a task, then those tasks can be placed together in a project and give you access to calendar, timeline, rules…
+1 vote
+1 vote
+1
+1