alexanderkoek opened a new issue, #30627: URL: https://github.com/apache/superset/issues/30627
### Bug description When using a time filter of type "Custom" and select "Specific Date/Time" and click on "now" I get the correct timestamp in local time.  However, when I select "Now" as time, the system selects the current time as UTC and not in the correct timezone.  In the Netherlands in summer time this means that the time is 2 hours behind (I clicked on the Now button around 14:59, but time is shown as 12:59), causing me to miss two hours of the most recent data:  Please, make sure the "Now" is implemented taking the correct timezone into account. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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-unsubscr...@superset.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
