SIP-74 sub-proposal: Turn on DASHBOARD_NATIVE_FILTERS feature flag by default

[suddjian]

Should we apply and remove the DASHBOARD_NATIVE_FILTER flag in Superset 2.0? Or maybe we should keep the flag but just turn it on by default?

What's required:

• A filter box migration script
• Sufficiently high feature quality (I'm not sure what current status is here, maybe someone can catch me up)

Do we want to apply the same treatment to the other related feature flags too? What additional prep might be necessary for them?

[tweinreich]

I think it would be great if features like DASHBOARD_NATIVE_FILTER would be enabled by default but still exist as flags (or admin menu options) to turn them off. In my opinion the experience of creating filters is much easier compared to using the filter box chart widget and jinja templating.

[junlincc]

we already turned said feature flag on by default 😅 and had a discussion to keep the FF until re reach 120% feature parity, which is current missing some complex use case of multiple filter boxes being a group of filters that limit filter value of each other. filter box code and the FF will both be removed after that.

[suddjian]

@junlincc If that work gets done before SIP-74 is finalized (which might be quite a while), then removing the flag would be a good addition. Otherwise it would be best left for a later major release.

Are there any issues or trackable things for that functionality, that we can link to from this issue? Linking to it from here will make it easier to do 2.0 planning.

[suddjian]

This was done apparently