All ideas

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

It would be great if you could add a target / goal line to a chart to measure distance / progress toward achieving a goal. Ideally, we would also be able to send an alert when the goal has been achieved.

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

As a business user, I want a no-code calculated column builder in Explore so I can define data visualizations without the help of a data analyst or engineer.

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

Right now you are forced to use SQL to do complex filtering (and + or statements, etc.) which can be difficult for non-technical end users. We'd ideally be able to support this type of filtering without the need for SQL

As a user, I want to edit chart styling (color, label position/size, etc.) in my dashboard. I want this so I do not have to go back into Explore to customize my chart and can make more holistic stying decisions within the context of the dashboard.

We need elegant ways to manage / select time zone from an end-user perspective. At the moment we do not have this functionality / are forced to use custom columns or dataset offsets to do this vs. a GUI.

As a user, when I go to search for "Line" chart the first row of search results are not what I would expect. Example: Area Chart shows above Line. I would expect that Line Chart would be the first thing that would show up. I have tried this also w...

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