All ideas

Currently, a lot of the language (in labels, helper text, tooltips, etc.) used in the application is data-domain and developer specific. This language can make it harder for non-technical users to navigate and understand, which hinders their workf...

In the dashboard email report modal, schedule dropdown fields are pre-populated with menu options. Remove this and replace with placeholder text.

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 ...

Current UI for selecting a datetime is clunky and inconsistent throughout the application. Use standard pattern for all datetime picker UIs.

When creating charts in Explore, adding configurations will change the chart query which is hidden from users. This makes it difficult to debug issues when a chart isn't working as expected.

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...

User have expressed difficulty with the sharing model, especially when it comes to sharing with a team and knowing who's on that team. Team information is only accessible from Manager, and most of the time users are in Superset where that informat...

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...

Enable better collaboration on charts and dashboards by integrating with project management tools