Feature Ideas

Allows for things like filter updates while viewing graphs near the bottom of a dashboard without having to scroll back to the top, change the filter, and then scroll back to your graph of interest.

Right now, certain elements of the custom canvas UI are fixed (e.g. the template popover screen, the 'cancel/add chart' buttons in the template edit UI). It would be great if that was something that could be fully customised so that it could fit with similar behaviours in teams' applications.

We're building a set of dashboards for customers to get insights into their Embeddables, including information on unique viewers, query performance, dashboard performance, error messages, and more.

Sometimes variables are being set as one type (e.g. text or boolean or number) but we want to use them as an input for a component that expects a different type. Automatic converting or casting of types (where it makes sense) could significantly reduce this problem. This problem comes up regularly when a control is designed to be reusable and thus its events always output strings, even though the dimension it came from might be a number of boolean, etc.

There might be scenarios where download options don't make sense (e.g. KPI charts) and clutter the UI. It would be good to have the ability to set this as chart-specific behaviour in the theme (currently it is a global setting

Prevent the latest component and model versions from automatically being selected in Embeddables. This would give users more control over which versions are used rather than always defaulting to the newest release.

Wouldn't it be amazing if there was a copy/clone button close to the Edit and Delete ones 🥺

Sometimes a part of a dashboard only makes sense to show once the user has selected an input.

End users can download their dashboard as a PDF

To make building dashboards in the no-code builder easier, we'll introduce the concept of 'containers' to layout components on the canvas

Currently dataset filters all use simple AND across each filter. It is, however, common that you might want to use OR instead, or a nesting thereof.

Something to ease a component prop migration, or to create a template in case we go into the hundreds of dashboards. E.g. a basic import/export JSON endpoint to configure an Embeddable

Make it easier for Embeddable builders to organise their Embeddables using folders.

It would be useful to be able to clone a dashboard from the live workspace to local dev preview so that it could be worked on locally

Enable users to schedule Embeddable delivery via email/Slack/Teams etc.