We would like Superset users to have a consistent, easily accessible way to jump into the creation flow for SQL Queries, Charts, and Dashboards. Here's what we propose:



cc @elibrumbaugh
This is something I've wanted to see for so long!
SG passing through the standard styles. Will keep an eye out on the other ticket/convo.
Removing the + from the CRUD UI is a huge usability improvement. Placement of this button seems pretty standard which is nice. I like the right aligned Filter action placement.
Q: Just to clarify this [new] button will persist through all pages?
Q: Just to clarify this [new] button will persist through all pages?
Yes! It will be part of the nav, so visible anywhere nav is visible.
I think "Add Filter" is a little more clear than "Filter Results". Filtering results sounds to me like I'm filtering on a search query I've already made.
Definitely open to suggestions here! Hopefully we'll hear input from others on this.
Tackled Filter Results here https://github.com/apache/incubator-superset/pull/6670
"Add Filter" doesn't make sense either. How about "Advanced Search" since the action of clicking on the funnel icon forces you to do an explicit search with parameters?
I'm tackling most of what's in here in #6670.
Beyond this, we'll need to improve the "New -> Chart" page, notably the "datasource has not yet been created" flow. Also we probably need a decent path to create charts from the context of a dashboard (currently I you can only add charts that have been created before you entered the dashboard edit page).
"Add Filter" doesn't make sense either. How about "Advanced Search" since the action of clicking on the funnel icon forces you to do an explicit search with parameters?
I would take "Filter Results" over "Advanced Search". Describing this as a filter on search results vs another search seems more clear to me.
How about "Filter List" or "Filter this List"?
Seems like we are trying to nail down the _right name_ for the content on the page. _Results_ implies some kind of previous search action. List is generic and would work for any page it is on, but perhaps we need to use something specific to the content type on the page.
Would there be a way for us to dynamically name the content that needs filtering? Ala _Filter Charts_, _Filter Dashboards_, etc.
Each of the CRUD sections is titled with "List ___" where "___" is Charts, Dashboards, etc. So it feels like it makes most sense to say "Filter List" since 1) it doesn't imply a previous search (like "Results" or "Search" may imply) and 2) user is actually applying the filter to that list.
Any concerns with going ahead with "Filter List" for now?
I'm okay with filter list but if we're going to say filter list should we just say filter?
Agreed. We should probably go through and review our copy for things like this. On the same UI it also says "List Charts" which we could change at the same time. I've created a ticket for this: #6710
Merged the related PR. Outstanding items:
Thanks for writing this up @mistercrunch. Could you share screenshots?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
Each of the CRUD sections is titled with "List ___" where "___" is Charts, Dashboards, etc. So it feels like it makes most sense to say "Filter List" since 1) it doesn't imply a previous search (like "Results" or "Search" may imply) and 2) user is actually applying the filter to that list.
Any concerns with going ahead with "Filter List" for now?