All ideas

Consider setting upper limits on the number of series that users can add to each chart type. For example, if a user adds 500+ series to a line chart, the chart will take a long time to render (and might time out) and end up being unreadable.

How does naming a tab relate to the query name when you save the query? Tabs should persist their order Tabs should reopen the latest one you were working on

Current gsheets db connection only allows connecting to one tab at a time. Allow users to connect to multiple tabs at once (toggle? or select sheets?) so that they don't have to get the URLs for each sheet

1) What is the problem or goal the end user is trying to solve or accomplish? Data Analyst needs to have the Y Axis chart adapt based on filter ranges applied. Currently certain outliers create a larger range Y-Axis, however, when those time range...

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