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
+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.
Black Breeze
•
May 8, 2025
Hi there 👋 — thanks for the feedback on Views.
We’d love to understand a bit more about your use case before jumping in. It sounds like you have quite a few Views—can you share:
What kinds of problems are these Views helping you solve?
Who creates them, and how often?
How do you usually find or reuse a View today?
What breaks or slows down when you can’t find the right one?
We want to make sure we’re solving the right problem—and not just smoothing over something deeper. Appreciate any context you can share!
Indigo Stew
•
Jun 16, 2025
@Marcin Wyszynski
What kinds of problems are these Views helping you solve?
views are allowing us to group common components, e.g. components deployed to cloud accounts as a part of baseline
Who creates them, and how often?
Created via automation, only added when a new component is deployed
How do you usually find or reuse a View today?
These views are heavily used for our cloud account provisioning
What breaks or slows down when you can’t find the right one?
Navigation is clunky - the titles aren’t wrapped in the UI so they can be hard to find. It would be nice to have a folder-like hierarchy, e.g.
This request was merged into another request
Comments3
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.
Black Breeze
May 8, 2025
Hi there 👋 — thanks for the feedback on Views.
We’d love to understand a bit more about your use case before jumping in. It sounds like you have quite a few Views—can you share:
What kinds of problems are these Views helping you solve?
Who creates them, and how often?
How do you usually find or reuse a View today?
What breaks or slows down when you can’t find the right one?
We want to make sure we’re solving the right problem—and not just smoothing over something deeper. Appreciate any context you can share!
Indigo Stew
Jun 16, 2025
@Marcin Wyszynski
What kinds of problems are these Views helping you solve?
views are allowing us to group common components, e.g. components deployed to cloud accounts as a part of baseline
Who creates them, and how often?
Created via automation, only added when a new component is deployed
How do you usually find or reuse a View today?
These views are heavily used for our cloud account provisioning
What breaks or slows down when you can’t find the right one?
Navigation is clunky - the titles aren’t wrapped in the UI so they can be hard to find. It would be nice to have a folder-like hierarchy, e.g.
AWS
Production
Component 1 View
Component 2 View
Test
Component 1 View
Component 2 View