Enhancement

Use of unintuitive icons as buttons is causing discoverability issues for users (e.g. pencil icon for adding filters, calendar icon for creating an email report). Where space allows, replace icon buttons with text buttons for clarity. Where space ...

Users want to be able to share quick ad-hoc data visualizations created from SQL queries. Currently, the paths to do so are: Share a saved query, which the other user must rerun and use to create the visualization. Create the visualization and sha...

Current "create" buttons in CRUD views are small and not immediately discoverable by users. Consider enlarging or moving to the top left next to the screen title.

Currently, Preset's information architecture is entity-drive (charts, dashboards, databases, queries, etc.), with one exception – SQL Lab. SQL functionality is a tool to help users create these entities, but may not make sense as its own sect...

For some users, the conceptual line between an individual chart and a dashboard is thin. Currently, the information architecture supports a very segmented organization and navigation between dashboards and charts, forcing users to go back and fort...

Users are experiencing confusion when connecting non-database data sources (Google sheets and CSVs). Problems1. Connecting a Google Sheet is located in the "Connect database" option. Users do not think of Google Sheets as a database and do not go ...

Stop the error before the job ID. We can then just have them look at Data - View Results for better formatted detailed error.

Current State: The current example datasets are not things that are widely relevant to our customers. Desired State: There are more examples across sales, product, engineering, and marketing with visualizations.

For instance I would like to apply a filter like: if the value of column 1 is greater than value of column 2. Right now you just can apply filters based on the value of one column

Favicon for Manager and Superset are different in Preset. It creates confusion.