+1
+1
We NEED this.
Would love to have this ability as well!
Hi. Are there any updates on this?
1 Like
+1
Highly needed
+1 for this as well!!! Would make much use of this as multiple teams need visibility into certain subtasks but they organize their parent tasks differently.
Yes please implement this!
Badly needed to enable more flexible work view management. A subtask might be part of a product feature, but at the same time be part of a project delivery item.
1 Like
I would love this feature as well!
This feature would be extremely helpful for our sub tasks that can be considered components of multiple tasks across multiple projects.
1 Like
This would be extremely helpful and unlock huge usability for us. I see this product feedback has been around for 5+ yrs, Is there any update from Asana as if this is being considered/possible?
1 Like
This is similar to what I think Asana needs, where you can roll up tasks under a milestone. Subtasks have their limitations, but if you could essentially group tasks under a milestone, so that once the tasks were completed the milestone would be complete this would be ideal. You can sort-of achieve this with dependencies, but itās still manual and messy.
This kind of seems like a basic functionality that exists in all other project management tools, but for some reason Asana missed it unfortunately.
3 Likes
Would be great to have this feature
1 Like
+1 vote for this feature!
1 Like
I also +1 this feature!! Please!
+1 pleaseeeeeee it has been years!!!
Iām always coming back to asana because it succeeds at being a flexible UI to represent whatās in my brain. The main area it falls short is this feature.
Hereās todayās example:
ā Iām managing a Product Roadmap; itās a Project.
ā Within the Project, I use Sections to organize the roadmap for easier consumption. Sections like ā2023 - Quarter 1ā, ā2023ā, āBacklog of āSandāā, and āOn the radar but not prioritizedā
ā Under sections, tasks represent shippable value. Itās what matters in this view: when does this value go live? A restaurant example could be something like āWeāre selling French Onion Soupā.
ā A subtask for āWeāre selling French Onion Soupā might be āget a buyer for onionsā. Another could be āupdate the menuā. But since our roadmap also includes āStay Open another hourā, you can imagine how āupdate the menuā could be a shared subtask.
Rather than a restaurant example, Iām experiencing this on a software development team. The subtasks I want to share are Engineering Epics like ābuild out an email serviceā. An email service isnāt value I want to see on the roadmap, but I do want to celebrate both āautomate new user onboarding emailsā and āadmins can approve PTO requests without logging inā. Each dependent on the email service subtask/epic.
1 Like
+1 for this feature!! This would be a game changer
+1 for this feature! More like +100 for my entire organization.
+1