-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BarChart (Legacy) doesn't take the timerange filter on dashboard #24398
Comments
When you say you updated to the current version, is that 2.1.0? Or 0.0.0dev (master branch)? This looks like an issue that should have been fixed by this #23865 which would be on 0.0.0-dev but not 2.1.0. |
Hi Sam, first thank you for your response :) When we will be finished at all. I will let you know her about our test result. |
That sounds good. So you know, 2.1.1 is currently being tested for release as 2.1.1rc1. So if you're looking for a version to test, you could run 2.1.1rc1, or wait for 2.1.1 to be officially released (likely in the coming weeks) and test it then. |
@ShabanGerber Superset 2.1.1 was officially released yesterday! Are you able to upgrade + see if your problem is resolved? |
@rusackas might want to change the status here |
Indeed, we're no longer officialy supporting 2.x, the legacy bar chart has been migrated away, and this thread has gone cold. Closing! :D |
The timerange Filter for the BarChart (Legacy) ist not working on the dashboard.
If you have a look in the generated sql query, you can not see the timerange was not used.
How to reproduce the bug
Expected results
We expect that the timerange filter will be used correct.
Actual results
the timerange filter is not used in barchart
Screenshots
If applicable, add screenshots to help explain your problem.
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: