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

   It's possible to map dashboard filters to specific tabs, so that they don't 
appear when viewing tabs they are not mapped to (they are considered out of 
scope).
   When hitting CLEAR ALL, required filters out of scope are also getting 
cleared, preventing the user from applying a new filter selection.
   
   #### How to reproduce the bug
   1. Create a chart, and save to a dashboard.
   2. Create a second chart and save it to the same dashboard
   3. Edit the dashboard, and add two tabs to it.
   4. Add one chart to each tab.
   5. Create two dashboard filters, make them required and map one for each tab.
   6. When viewing a particular tab, click on **CLEAR ALL**.
   7. Apply a new value for the only required filter for this tab.
   
   ### Expected results
   The user is able to apply the new filter combination, given there's only one 
required filter for this tab.
   Required highlights should be removed for out of scope filters 
   
   ### Actual results
   The user is blocked from applying a new filter combination, unless all 
required filters (from all tabs) are re-filled. 
   
   #### Screenshots
   
   
![image](https://github.com/apache/superset/assets/10627051/b1ffc3e3-a41b-439e-8e8b-124ab5244fb8)
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version:
   - superset version: `master`
   - python version: `python --version`
   - node.js version: `node -v`
   - any feature flags active:
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   


-- 
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