Feature Request: A way to aggregate and view tasks across a set of projects in a Board view based on filterable criteria with support for Grouping and Subgrouping without relying on multihoming.
Example in Action
Here’s an example of what this looks like. Below you can see tasks from multiple projects in a single Board view grouped by status and sub-grouped (swimlanes) by project.
Current State
Asana’s Advanced Search allows viewing tasks across multiple projects in a list format. However, this capability is limited compared to what’s possible within individual project views:
- Advanced Search results only display as a list. Board view is not supported.
- Advanced Search does not support custom task types as an input. Advanced Searches can return custom task types in the output, but there’s no option to filter based on them.[1]
- No ability to group or subgroup results by anything like we can in projects. e.g., users cannot group the output by project, custom task type status, custom fields, assignee, etc.
Requested Functionality
Develop the ability to see tasks across project views with the same flexibility available in single-project views:
- Board/Kanban view for search results. Allow switching between list and board layouts when viewing tasks across projects.
- Grouping and subgrouping. Enable organizing results by multiple dimensions. For example: group by custom task type status, then within each status group, display rows by project.
- Custom field display control. Enable the same functionality from Board views now which to let users choose which fields appear on cards or are visible as columns in lists.
Limitations to Consider
When grouping or subgrouping by fields that don’t exist on all tasks, edge cases will arise:
-
Grouping by custom task status. Tasks can only display under a status column if they belong to that task type. Tasks of other types (or no type) would need to fall into a “No Status” or “No Type” column. To address this cleanly, the view should support filtering to a specific task type so only relevant tasks appear.
-
Subgrouping has the same constraint. If subgrouping by a field tied to a specific task type, the same filtering capability would be needed to avoid cluttering the view with tasks that can’t be meaningfully categorized.
-
Custom fields not present across all projects. When grouping by a custom field that doesn’t exist on some projects, tasks from those projects would lack a value for that field. These would similarly need a fallback group (e.g., “No Value”) and ideally we users could collapse that section or column just like they can currently in list and board views within projects.
Use Case
Managing work across related projects requires seeing the full picture without constantly switching contexts.
A cross-project board view grouped by project with status columns would allow tracking progress across an entire portfolio while maintaining the visual workflow benefits of kanban, something currently only possible one project at a time or by using workarounds like multihoming everything into a universal project.
Existing feature request for this: Task Types Status Searchable with Advance Search ↩︎