Make sure these boxes are checked before submitting your issue - thank you!
0.999.0dev
I set the time range for the Filter Box in explore is "No Filter". But when on dashboard by default it will show "Last Week". So how to fix it?
I have checked from 0.28 to 0.29.0RC7, this bug has not fixed.
I suggested to escalate this bug to top priority because it will lead un-using for whole Superset.
+1
I met the same problem
I met the same problem
Can't reproduce on master
I am also having the same problem. I also suffer from the filter box disappearing from the dashboard when selecting a new time range. You get the following javascript error:
Uncaught TypeError: Cannot read property 'map' of undefined
at filter_box.885b5b9fd31f4d3caa48.chunk.js:2
at Array.forEach (
at t.
at t.
at Qi (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
at Xi (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
at to (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
at Ro (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
at No (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
at ha (vendors-major.4f5a17619ab655ae0e0c.chunk.js:2)
Cant we change "Relative to today" to "Relative to now"? Because Relative to today starts showing data from present day's 00:00:00 right?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.
This bug has not been fixed, why marked as stale?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.
This issue should be solved asap because this is very very misleading.
Can we have someone take a look at this? We've had this as a problem for a few months now and this is the most recent place I've seen any update on the subject.
Most helpful comment
I have checked from 0.28 to 0.29.0RC7, this bug has not fixed.
I suggested to escalate this bug to top priority because it will lead un-using for whole Superset.