parag2131 opened a new issue, #36876:
URL: https://github.com/apache/superset/issues/36876

   ### Bug description
   
   In dashboards using Native Filters, clicking Clear All only resets the 
filter UI state but does not actually apply the change until the user manually 
clicks Apply Filters.
   
   This behavior is unintuitive and leads users to believe filters are cleared, 
while the dashboard data remains filtered until Apply is clicked.
   
   Environment
   
   Superset version: 5.x / 6.0.0
   
   Dashboard with Native Filters
   
   Default filter behavior (no custom flags)
   
   Steps to reproduce
   
   Open a dashboard with Native Filters
   
   Apply one or more filters
   
   Click Clear All
   
   Observe that:
   
   Filter controls reset
   
   Dashboard data remains filtered
   
   Click Apply Filters
   
   Dashboard finally updates
   
   Expected behavior
   
   Clicking Clear All should:
   
   Immediately clear all applied filters
   
   Trigger the filter application automatically
   
   Update the dashboard data without requiring an additional Apply click
   
   Actual behavior
   
   Clear All only resets filter inputs
   
   Filters are still applied until Apply is clicked
   
   Users must perform two actions for a single intent
   
   Why this matters
   
   “Clear All” strongly implies a completed action
   
   Requiring Apply after Clear All is confusing for users
   
   This behavior differs from most BI tools and UX expectations
   
   Causes frequent user errors and support questions
   
   Suggested solutions (one or more)
   
   Automatically trigger Apply when Clear All is clicked
   
   OR provide a setting:
   
   “Auto-apply Clear All”
   
   OR make Clear All bypass Apply entirely
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   6.0.0
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### 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.
   - [ ] 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to