adam-stasiak opened a new issue #15639: URL: https://github.com/apache/superset/issues/15639
When I revisit native filter configuration then I can't see that this filter was configured with default value. When I click on this again - the previous value is retrieved. ### Expected results Component should show that someone configured this filter with some value. ### Actual results Component state is not set correctly. I have to click on this. #### Screenshots https://user-images.githubusercontent.com/25153919/125347356-1d6ace00-e35b-11eb-9c94-22a3ad9e6981.mov #### How to reproduce the bug 1. Go to dashboard 2. Add native filter with value added in "Filter has default value" 3. Save 4. Revisit filters configuration panel and check if checkbox is set. ### Environment (please complete the following information): - superset version: `superset version` - python version: `python --version` - node.js version: `node -v` ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context -- 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]
