You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/03/01 17:01:52 UTC

[GitHub] [superset] jinghua-qa opened a new issue #18985: [Native Filter] default number filter is not working properly when user choose max/min in single value

jinghua-qa opened a new issue #18985:
URL: https://github.com/apache/superset/issues/18985


   When user setup a default value for number filter, then user select single value for the number filter and change the number to be maximum or minimum, the default value did not stay on the selected value.
   
   #### How to reproduce the bug
   
   1. Go to native filter and setup a number filter
   2. Select single and choose max or min
   3. Select default value for the filter and save changes
   4. Go back Native filter configuration, and check default value
   5. Change the single value and save
   6. Check the default value on native filter on dashboard view
   
   ### Expected results
   
   1, in native filter, default value will be in <= single value or >= single value range 
   2, in dashboard view, native filter default value will reflect the change
   
   ### Actual results
   
   1, default value bar will change to max or min number, not reflecting the correct range
   2, in dashboard view, native filter default value did not reflect the change
   
   #### Screenshots
   
   https://user-images.githubusercontent.com/81597121/156213408-097c4e05-268f-414a-a7dc-9b2f55799790.mov
   
   
   
   
   
   ### 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.
   
   ### Additional context
   
   Add any other context about the problem here.
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org