Skip to content
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

Open
arikfr opened this issue Oct 20, 2015 · 17 comments
Open

User configuration for date/time format & default timezone #618

arikfr opened this issue Oct 20, 2015 · 17 comments

Comments

@arikfr
Copy link
Member

arikfr commented Oct 20, 2015

See #617 and #411 for more details.

This was referenced Oct 20, 2015
@karlgrz
Copy link

karlgrz commented Jan 19, 2016

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.

@arikfr
Copy link
Member Author

arikfr commented Jan 19, 2016

If all your users need MM/DD/YYYY, then you can change it in the global configuration (by adding the REDASH_DATE_FORMAT environment variable).

@karlgrz
Copy link

karlgrz commented Jan 19, 2016

@arikfr fantastic tip, thank you! Works beautifully.

@jeffwidman
Copy link
Contributor

In the Docker environment, where do I set this REDASH_DATE_FORMAT ?

@arikfr
Copy link
Member Author

arikfr commented May 4, 2016

@jeffwidman it's an environment variable you need to set. If you use Docker Compose, then it's in the environment section of the YAML file.

@deecay
Copy link
Contributor

deecay commented Feb 20, 2017

I get a lot of request for absolute-time display.
Not "13 days ago" but "4 May 2016" instead.

Proposal:

  1. Replace all occurrences of span am-time-ago to rd-time-ago.
  2. Introduce new env variable REDASH_ABSOLUTE_DATE and make rd-time-ago respect that.

@arikfr
Copy link
Member Author

arikfr commented Feb 20, 2017

@deecay I prefer not to complicate things too much, here's an alternative: show absolute time when hovering over the relative one.

@deecay
Copy link
Contributor

deecay commented Feb 20, 2017

How about relative AND absolute shown together? Often too long and ugly?

@arikfr
Copy link
Member Author

arikfr commented Feb 20, 2017

too long...

@deecay
Copy link
Contributor

deecay commented Feb 20, 2017

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?

@RichardJohnn
Copy link

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".

@JohnGnotek
Copy link

No answer to RichardJohnn's question? I think many of us could use that answer.

@YDKK
Copy link

YDKK commented Feb 9, 2018

Hi.
Is there any way to configure dateTimeFormat manually?

I'd like to see seconds or milliseconds in the result of query.
It seems like set by here.
I think it would be better if dateTimeFormat can be configure from environment variable like REDASH_DATE_FORMAT.

@RichardLitt
Copy link

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 help-wanted: if someone wants to jump in with a possible PR, we'd gladly look at it.

@itssimon
Copy link

@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.

@dobesv
Copy link

dobesv commented Jan 12, 2021

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.

@azundo
Copy link
Contributor

azundo commented Apr 29, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.