TL;DR: Requesting the ability to apply saved tab configurations — including custom views, filters, sorts, and groupings — to existing projects post-creation, either individually or pushed across multiple projects at once via bundles.
I manage a tech stack portfolio with 70+ projects. Every project shares the same three bundles, which works well for keeping things consistent. But I also need each of those projects to have the same set of custom view tabs — each configured with specific filters, sorts, and groupings depending on what the team needs to see.
Right now, I can build those tab configurations into a project template. But once a project exists, there is no way to apply or push that configuration to it. The only option is to manually set up each tab, on each project, one at a time. At 70+ projects, that’s not a realistic ask.
What I’m requesting is one or both of the following:
- Apply a template to an existing project — specifically the tab/view configuration defined in the template, not just tasks
- Push tab configurations via bundles — since bundles already propagate shared structure across projects, extending that to include saved view tabs would solve this at scale
This has real impact for any team managing a large portfolio where consistency across projects matters. Right now, bundles get you partway there but leave view configuration as a manual, per-project task.
I’m aware of this existing thread: Using Templates In An Existing Project . At first glance these may look like duplicates, but Asana’s product has evolved significantly since that post was written in 2019. Bundles didn’t exist then, templates are far more sophisticated now, and the gap I’m describing is specifically about view tab configuration — not task structure or CSV imports, which is what that thread focused on.
Would love to see this on the roadmap, particularly the bundle-based propagation angle since that’s the most scalable path for large portfolio management.