Filter presets for dashboards: saved sets, defaults, out-of-sync sync

Baseline Apache Superset has no concept of filter presets — every analyst re-enters the same filter combinations on every visit. Our fork adds saved filter sets as a first-class sidebar panel, with a default per dashboard, out-of-sync warnings, and one-click synchronization when the dashboard's filter structure changes.

Side-by-side

See the difference

This capability has no Apache Superset 4.1 equivalent — there's nothing to slide against. Open the fork screenshot for a pixel-level look.

BaselineApache Superset 4.1 (baseline)No baseline equivalent

No baseline equivalent

Not available in Apache Superset 4.1

Stock Superset has no concept of saved filter sets at the dashboard level. Native filters exist, but every analyst re-enters the same values on every visit — there is no way to persist, share, or default a filter combination.

Our forkdrafted.work fork

Guided tour

How the filter sets panel is built

Hover or tap a pin to see how each control in the filter sets panel maps to a real analyst workflow. The panel is designed to be obvious — presets are one click away, and their state (default, out-of-sync) is visible at a glance.

Annotations

Preset editor

Inside a preset: saved values, sync, and the apply-first gate

Opening a preset's settings surfaces the full editor — name, the exact filter values the preset snapshots, a default marker, and the sync action. Nothing like this exists in baseline Superset, which has no preset object at all. The editor also enforces the apply-filters-first workflow so a stale preset never silently overwrites current work.

BaselineApache Superset 4.1 (baseline)No baseline equivalent

No baseline equivalent

Not available in Apache Superset 4.1

Baseline Superset has no preset editor because it has no presets. There is no place to name, default, inspect, or synchronize a saved filter combination at the dashboard level.

Our forkdrafted.work fork

Inside the modal

How the preset editor is built

Each annotation explains one building block of the modal. The editor deliberately mirrors a form rather than a config blob — every field is visible, nothing is hidden behind advanced toggles.

Annotations

Context

Why this matters

A dedicated FILTER SETS panel lives at the top of the filters sidebar. Analysts pick a preset in one click and the dashboard reloads against a saved combination of filter values — time range, currency, segment, metric, everything the dashboard exposes. Each preset has its own quick actions (default, sync, settings) right next to the name, so switching between workflows doesn't require opening a modal.

When a dashboard's filter structure drifts from a saved preset — someone adds a filter, renames a metric, shifts a grouping — a yellow warning triangle appears next to the affected preset, and the preset editor offers a one-click SYNCHRONIZE action that reshapes the preset to match the current structure. The gate is explicit: you apply filters first, then save the updated values, so a stale preset never silently overwrites fresh work.

A single preset per dashboard can be marked as the default — that's the one every user lands on when they open the dashboard. Defaults are scoped per dashboard and coexist with personal saved sets, so a board owner can ship a sane starting point while individual analysts keep their own saved combinations alongside it.

Related features

Capabilities that usually ship alongside this one. Package tags tell you where each feature lives in our delivery plans.