erquhart
erquhart•5mo ago

Feature request: saved filters in the dashboard

Would be cool to have the ability to save and name a filter, values and all, for a given table. Would use this a lot, and it would probably increase my usage of the dashboard in general.
7 Replies
erquhart
erquhartOP•5mo ago
One potentially simpler approach, provide a recent filters list to choose from. Even without custom naming, would provide a lot of the value of the full feature.
ari
ari•5mo ago
Saved views are definitely on the radar! Thanks for the request, helps bump up the priority
erquhart
erquhartOP•5mo ago
Data point: been doing some heavy data investigations, multiple dashboard tabs side by side, and recent filters would have been even more useful than saved filters, honestly. A whole lot of one-offs that I wouldn't normally take the time to save. I often wanted to use the browser back button to get to the last filter in the current table, which doesn't work (and that's understandable).
ari
ari•5mo ago
Yup, I'd agree with that! I felt a similar way when building the "Run history" in the function runner -- seeing the most recent arguments provides most of the value that bookmarking some arguments/queries does. There's definitely additional value, but we'll be focusing on recent things first. I'll have to think a bit more about whether the back button should include filter state - it could be annoying if you actually want to use navigation to go back to the last real page
ari
ari•5mo ago
Recent quote from @Indy in our internal slack 😄
No description
erquhart
erquhartOP•5mo ago
Yeah that's why I said back button behavior is understandable, you could end up with a long history of stuff you didn't expect to be there. Recents should fill the gap just fine imo.
ari
ari•5mo ago
We shipped a filter history on the data page for everyone today ( @erquhart had early access to it )