graceguo-supercat opened a new issue #14744:
URL: https://github.com/apache/superset/issues/14744


   Current Select type filter component has `time range` control, but doesn't 
offer a `time column` control. For a dataset has multiple time columns, this 
will introduce a potential data quality issue.
   
   #### Screenshots
   This is screenshot to explain filter_box usage: A filter field, which is not 
a `Date filter`, it can still have `time range` and `time column` to limit the 
available choices.  For example, with "Last 180 days" time range, this filter 
has 6 options, while without 180 days limit, it will show 8 options:
   
![Screen_Shot_2021-05-20_at_11_25_40_PM-2](https://user-images.githubusercontent.com/27990562/119094656-2b891780-b9c6-11eb-8d14-e14c7699fe79.jpg)
   
   
   
   ### Environment
   
   latest master
   
   ### 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
   
   I remember we discussed this issue in the next version of filter configure 
modal design. So i assume @junlincc is aware of this issue. I created an issue 
is to make sure backend can handle the extra query parameter for native filter 
component. cc @villebro 


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

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