Hi, I’d like to submit a feature request / product feedback regarding subtask visibility and filtering.
Our team uses Asana for simple project and task management, where subtasks are the primary unit of work and the only level where we assign due dates.
Currently, there is no way to filter or sort a Project view by subtask due dates, or to see all subtasks with due dates across a project in one unified view. This creates a major visibility gap and requires manual review of each parent task to understand what work is actually due.
We are requesting:
The ability to include subtasks in Project-level filters
The ability to filter/sort by subtask due date, assignee, and status
A unified “all tasks + subtasks” view within a project
This limitation is significantly impacting our ability to manage deadlines and workflow efficiently.
Please route this to the product/feature team, and let me know if additional detail would be helpful.
Just upvoted this! This is a huge limitation for our team; we just rolled out some flows with subtasks and this makes visibility of these tasks so much harder.
Until/if this request is implemented, perhaps consider these workarounds if you haven’t already.
If you homed (added to a project) those subtasks, then you could use that project to easily provide the filters and views you need. This could be automated, potentially, with rules or templates, depending on your workflow.
A related approach would be to home those subtasks to the very same project their parents are in, offering the same benefits, but with a a side effect. That’s all explained in another answer I gave to a related question:
Finally, advanced search saved (starred) reports may offer limited relief too, since you can specify “subtask” as a criterion in the search (though be aware it means any level of subtask, not just the first level).
Thank you for the feedback on current workarounds. Our team has tried these work arounds and they only further add to the stress of trying to ensure all tasks are being taken care of.
We rely on Asana as a straightforward task management and collaboration platform. Our workflow is intentionally simple:
Projects → matters/customers
Tasks → phases or categories of work
Subtasks → actual actionable items with assigned owners and due dates
In practice, subtasks are our primary unit of execution.
Core Limitation
Currently, there is no reliable way to:
Filter or sort a Project view by subtask due dates
View all subtasks with due dates across a project in a single, unified view
Consistently include subtasks in standard filters (e.g., “Due this week,” “Overdue”)
This creates a significant visibility gap. At the project level, we cannot easily determine what work is actually due or in progress without manually opening each parent task.
Feedback on Suggested Workaround
We have tested the commonly suggested workaround of “homing” subtasks into projects (i.e., adding subtasks to the same project as their parent). In practice, this introduces substantial friction and undermines the reliability of the platform:
Manual dependency & error risk:
The workflow depends on every team member remembering to manually add subtasks to the project. Any missed step results in incomplete or inaccurate visibility, which is unacceptable in a deadline-driven environment.
Ongoing administrative overhead:
Subtasks must be manually added when created and often removed upon completion, creating unnecessary, non-value-added work.
Breakdown of task hierarchy:
Subtasks effectively become duplicated or semi-independent tasks, weakening the intended parent-child structure and making it harder to understand relationships between work items.
Project clutter and duplication:
Subtasks appear both under their parent task and separately at the project level, leading to visual clutter and confusion about what has been accounted for.
Loss of organizational clarity (Sections):
Subtasks added to projects are often surfaced at the top or outside their parent task’s section, making it difficult to determine where they belong within the workflow.
Reduced reporting and filtering accuracy:
Mixing true tasks with manually surfaced subtasks results in less reliable and harder-to-interpret filtered views.
Poor scalability and adoption risk:
As teams grow, reliance on manual steps increases the likelihood of inconsistency. It also creates friction in onboarding and reduces compliance with the system.
Misalignment between tool and workflow:
Our workflow is simple and logical—subtasks represent the real work. The workaround forces us to adapt our process to the limitations of the tool rather than the tool supporting how teams naturally operate.
In short, this workaround introduces manual steps, data inconsistency, and structural confusion, which undermines the platform’s effectiveness as a task management system.
Requested Enhancement
We would greatly benefit from the following capabilities:
1. First-class treatment of subtasks in Project views
Optional toggle: “Include Subtasks in View”
2. Full filtering and sorting capabilities for subtasks
Filter by subtask due date, assignee, and status
Sort all items (tasks + subtasks) by due date within a project
3. Unified “All Work” view within a Project
A flattened view of all actionable items regardless of hierarchy
Ability to group or sort by due date, assignee, or parent task
Why This Matters
Many teams, including ours, use subtasks as the primary execution layer, not just supporting detail. Without project-level visibility into subtask deadlines, the platform loses effectiveness as a true task management system.
Addressing this limitation would:
Improve clarity and accountability at the project level
Reduce reliance on error-prone workarounds
Better align Asana with real-world team workflows
We value Asana’s simplicity and project structure, which is why we’ve continued using the platform. Resolving this issue would significantly improve our ability to manage work effectively within your ecosystem.
Thank you for your consideration. I’m happy to provide examples or further detail if helpful.
Tasks → phases or categories of work jumped out at me. My previous workarounds, which I understand aren’t helpful, were generic suggestions.
It’s always very dangerous to make specific suggestions without proper Discovery sessions, so take this with a grain of salt.
I work with many clients and in past situations that may be like this, I’ve advised using a single- or multi-select Phases/Categories custom field for those groupings which would promote your subtasks to tasks, and put you better in line with Asana’s design and expectations for use. A default tab where Group is set to that custom field (and hide empty groups) would mimic your task-level groupings, do so dynamically, and without shortcomings of using Sections for such groupings. Again, I don’t know the full extent of your workflow so I recognize this might not be a solution, but many clients found these kinds of “pivots” in project organization and display eye opening, and often very quick to try out.
Perhaps consider if you haven’t ruled out already.