Dashboard filter default value overridden by sticky last-used value (v1.62.2.14), is there any way to disable this per-dashboard?

[azzammasood]

We're on self-hosted Metabase v1.62.2.14. We have several dashboards with dashboard
filters that have an explicit Default value configured (e.g. a Date filter defaulting
to a relative range).

Behavior: once any user manually changes a filter's value on a dashboard, that value
is remembered per-user, per-dashboard, and is re-applied automatically the next time
they open that same dashboard, even though the filter still has its own configured
default. The dashboard's ... menu does offer "Reset all filters," which correctly
restores the configured default, but users have to know to do that manually each time.

We ruled out the cloned-dashboard/duplicate-filter-ID bug from
Sticky filters in version 50 (fixed in 50.10) —
our instance is on 1.62.2.14 and none of our dashboard filters share duplicate IDs, so
this looks like expected/by-design sticky-filter behavior, not that bug.

This matches what's described here:

Dashboard filter sticks to the same value despite having default value

So I was updating to Metabase 0.50.15 , and when trying the Dashboard filter, the filter value seems to stick to same value when I close and open the dashboard again. Steps to replicate : Open a dashboard and change a dashboard value , example date filter has default value "Last 7 days" change to "Current Year" Go back to collections, open the dashboard again. The date filter has "Current Year" value instead of the default value "Last 7 Days" Is this a known feature or issue, I cant find any…

where a default value gets overridden by a user's last-used value with no apparent way
to opt out.

Questions:

1. Is there any instance-level or per-dashboard setting to disable "remember last used
   filter value" and always fall back to the configured default?
2. If not, is this tracked anywhere as a feature request? We'd like to weigh in, for
   our use case, dashboards should reliably open in a known default state rather than
   silently carrying over whatever a user last selected, especially since most viewers
   don't know to use "Reset all filters."

Happy to share more repro details (dashboard/filter API payloads, screenshots) if useful.

[AndrewMBaines]

We worked around it by using either the API or direct to the underlying SQL to delete all the presets. I can’t remember which was deployed (not my customer).

Pain was timing the reset as you don’t necessarily want it being reset too frequently.

I’d prefer to see a ‘reset filters’ action button. Easy enough to deploy if self-hosted.