Saved view tabs are awesome. But, currently, they cannot be set as ‘Controls’ within a Bundle so that saved view tabs can be predefined and applied instantly to projects within a Bundle’s control.
Currently, you need to set up view tabs manually in each project since they are also not suported currently by Project Templates. Current workaround is to a create duplicate of a regular project, which unfortunately loses out on all the functionality of Project templates.
I have so many bundled projects that I just need to update all the views for, but the only way to do this is to go to each project manually and update it. You also can’t save views in project templates, so you can’t even have them set correctly from the start.
Same here. This would be an excellent update - establishing Bundles as another way to basically templatize certain kinds of projects that don’t require time-bound due dates or Role-based assignees.
On a side - it would be super helpful in Templates, as well!
Apologies if this is a duplicate but I couldn’t find it anywhere.
I’ve got dozens of projects that leverage a specific bundle for rules, custom fields, sections, etc. In order to efficiently present information to my teams, there is a specific filter/sort that I need to apply to a list view. Currently I can’t find a way to automate or templateize this, and as a result I’m stuck manually creating a new view, applying the filters & sorting, and saving it, one. project. at. a. time.
Bundles should absolutely be able to do this, no? Particularly since they facilitate the addition of the custom fields and sections that I want to filter and sort by!
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.
Please implement this, managing 400+ projects with bundles means it’s no longer feasible for me to manually go through each project anytime I add a new field
My only saving grace is that I make most of the fields private, so at least my team mates don’t see the mess that the list view has become.
! But per 
