Default native filters values don't set correctly about superset HOT 1 OPEN

Right... but personally, I don't see this as a bug. When two users open a dashboard (with or without default filter values in place), they're given a native_filters_key which you can see in the URL. Essentially, their state of filters is stored, and they can adjust these as they see fit without affecting other users.

If a default filter value is then added, the other users of that dashboard are already off to the races with their "fork" of the filters values. If we made it so that adding a default value nukes everyone's filter state, that would be problematic. I'm sure there's some way to have the setting of a default value go through all users' filter settings and apply that default wherever some users have that particular filter to empty.... but that might cause other issues too (like if they want it to be empty).

We're open to proposals here, but I think that the current implementation works, and the alternatives are a bit convoluted.

from superset.