I would like to see a new "Views" tab with Selected Views
Currently, the “Views” tab under “Stacks” has saved views of All, Private, and Shared. We have a large number of shared views that are created by members of multiple teams. Each team is often only interested in seeing their own Views. However, there is no way to filter the shared views, so we have to scroll and find the view we are interested in from among the other teams' shared views.
It would also be nice if we could select whether the view we see when clicking “Stacks” would default to “Views” or “Filters”.
Log in to comment and vote
Comments7
Teal Mongoose
Jul 28
•Merged request
•2 votes
View Organization
Views currently have no organization capabilities in the GUI, it’s simply a long list of views that cannot be searched except with CTRL+F. Please make these groupable/searchable
Sapphire Chipmunk
Jul 2
+1 — we create views programmatically via Terraform (spacelift_saved_filter) and are about to hit 150+ shared views across ~50 teams.
Today there's no way for a user to quickly find their team's views without ctrl+F. A search input would be the minimum viable fix. Longer term, grouping by prefix or folder hierarchy (as suggested above) would be ideal — our views already follow a naming convention like "<team> - config repos", so any prefix-based grouping would work out of the box.
We'd also benefit from the ability to restrict view visibility to specific teams or spaces rather than sharing globally with the entire account.
Sapphire Chipmunk
Jul 2
We're in the same boat. We automate view creation via Terraform — 3 views per team (config repos, team & iam, pr stacks). With ~50 teams, that's 150+ shared views and growing.
The biggest pain points for us:
No search field in the views list — users resort to ctrl+F
No way to scope views to a team — everything is global
No favorites or pinning — every user sees the full list regardless of relevance
A "Favorites" tab as suggested above would help a lot. Even a simple search/filter input at the top of the views list would be a big improvement for accounts at our scale.
Lime Koala
Jul 21, 2025
I apologize for not having responded earlier. I did not see a notification that there was a response. I met with our account rep last week, and she showed that this comment was here, so I wanted to respond.
First, I know I listed this second, but being able to default to the Views, instead of Filters would be the first thing I would like to see. The Filters tab, and the flexibility it allows, is much appreciated, but I rarely use it for anything other than building a View that I will then share. The inability to default to Views, pretty much guarantees at least one extra button click.
To answer your questions:
What kind of views do you and your team save most often? - I am almost exclusively using labels for my saved views. I use labels to categorize stacks by the types of resources and/or cloud a stack is managing.
What’s different about a view that’s worth sharing vs one that’s not? - The only view that I have created that I have not yet shared is for a new OpenTofu project with which I am still experimenting. In this case, I don’t see a reason for others to need to view these stacks yet. I could see
How often do you find yourself scrolling through shared views you don’t need? - Every time I need to look at stacks. I have to click “Stacks”, change to “Views” and find the view I’m interested in.
What’s the problem this is solving for your team today—speed, clarity, visibility? - Views allow us to focus on a subset of stacks to have on screen. The majority of my stacks use shared code bases, so I prefer to be able to see at a glance whether making a change has caused more plans than intended. This also makes it easy to verify that the correct stack has started its plan.
If you could wave a magic wand and improve this, what would change? - First, I think defaulting to “Filters” or “Views” should be customizable. I much prefer “Views” to be displayed. Within “Views”, there should be a “Favorites” tab, in addition to the “All”, “Private”, and “Shared” tabs to which we can add frequently used views from among both private and shared views.
Black Breeze
May 21, 2025
Thanks for sharing this! We’re curious to understand more before jumping in.
Right now, it sounds like you’re using shared views to organize stacks across teams—but that the list has gotten noisy. Before we explore filtering, we’d love to understand the job behind these views:
What kind of views do you and your team save most often?
What’s different about a view that’s worth sharing vs one that’s not?
How often do you find yourself scrolling through shared views you don’t need?
What’s the problem this is solving for your team today—speed, clarity, visibility?
If you could wave a magic wand and improve this, what would change?
We’ve seen teams use Views for everything from dashboards to ownership tracking, so we want to make sure we’re solving the right thing—not just tweaking the surface.
Thanks again—keen to hear more!