-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
User configuration for date/time format & default timezone #618
Comments
Any priority on this issue? We have to convert DD/MM/YYYY to MM/DD/YYYY manually ourselves, which is a bit annoying. Our queries return time in MM/DD/YYYY, as confirmed by looking at our redash db. |
If all your users need MM/DD/YYYY, then you can change it in the global configuration (by adding the |
@arikfr fantastic tip, thank you! Works beautifully. |
In the Docker environment, where do I set this |
@jeffwidman it's an environment variable you need to set. If you use Docker Compose, then it's in the |
I get a lot of request for absolute-time display. Proposal:
|
@deecay I prefer not to complicate things too much, here's an alternative: show absolute time when hovering over the relative one. |
How about relative AND absolute shown together? Often too long and ugly? |
too long... |
Yeah, it is. I can live with hover solution. How about my 1st proposal? I assume am-time-ago and rd-time-ago are interchangeable. Are you thinking of refactoring to one way, or are they separate for a reason? |
Is user configuration for default timezone on the radar? In our case it'd be too much to ask the user to think in terms of UTC and adjust the time for us. This means I can't reliably interpret a $humanTime like "yesterday 5am". |
No answer to RichardJohnn's question? I think many of us could use that answer. |
Hi. I'd like to see seconds or milliseconds in the result of query. |
At the moment, this isn't on the immediate radar. However, we would love to have help on this issue. I'm tagging this as |
@arikfr Is there any chance that the implementation of proper timezone support (with a user or organization setting) will be considered soon? I think this is an incredibly important feature to have for our users. |
If you want this you will have to implement it yourself and submit a pull request for it. Ideally I think it would use the browser's time zone instead of requiring a setting. |
I would vote against doing this based on a browser timezone. Many organizations have now gone fully remote and have staff spread across timezones. I would prioritize making query results consistent across users vs individual localization. Metabase's model fits our use case well where we can set an install-level timezone and the query engine both sets the sessions timezone properly (so date_trunc on timestamps with timezones works as expected out of the box) and display is consistent across all users. We're definitely having to fight a lot more with redash when aggregating metrics by day/month/etc. |
See #617 and #411 for more details.
The text was updated successfully, but these errors were encountered: