Bug description
This bug is that the Apply filters button won't be clickable unless all filters are updated/modified.
Screenshots/recordings
https://github.com/user-attachments/assets/7243bd38-681d-4f93-a47b-4bd59b586e8d
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Firefox
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @Pegoku! I'm Dosu and I’m helping the superset team.
The "Apply filters" button is disabled if any required filter is missing a value or has a validation error, even if other filters have been changed. This is controlled by the checkIsApplyDisabled function in the FilterBar component, which checks for validation errors, unchanged filter states, and missing required values. As a result, the button can appear unclickable unless all required filters are set, which can feel like you must update every filter before applying changes. This is strict validation logic, not a recent regression, and recent changes (like accessibility or dependent filter improvements) haven't altered this core behavior. If you want to relax this requirement, it would involve changing the logic in checkIsApplyDisabled to allow partial filter updates or to only require that changed filters are valid and set.
See FilterBar logic
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: rusackas
I think the bot is correct here, but let me know if you find otherwise!
It might be a bit of confusing theming/styling here (cc @msyavuz ) but I suspect that what's happening is you have the filter set as "required" and it's suggesting a default value, but not applying a value until one is selected. It might be that it just looks like the 1 is selected, even though it's not?
Can you confirm whether or not the "Filter has a default value" box is checked on that filter?
