You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
native filter values is not sorted when select "Sort filter value" in Advance
How to reproduce the bug
Repro steps
1, create value filter for "Video Game Sales" dashboard, select 'Genre' column to filter
2, select Sort filter value in advance
3, observe filter value order on the left panel in dashboard
Expected results
Values in table should be filtered
Actual results
Values isn't filtered as expected
Screenshots
Screen.Recording.2022-01-10.at.3.01.56.PM.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!
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
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
native filter values is not sorted when select "Sort filter value" in Advance
How to reproduce the bug
Repro steps
1, create value filter for "Video Game Sales" dashboard, select 'Genre' column to filter
2, select Sort filter value in advance
3, observe filter value order on the left panel in dashboard
Expected results
Values in table should be filtered
Actual results
Values isn't filtered as expected
Screenshots
Screen.Recording.2022-01-10.at.3.01.56.PM.mov
Environment
(please complete the following information):
python --version
node -v
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: