|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The core problem is that each user can have a different timezone. This means that you are annoying the heck out of some people.
Some things to mitigate this include:
1) Using more relative times. These are always useful, though they become stale if the page isn't refreshed or reloaded.
2) Adding timezones to times. (e.g. JENKINS-13092)
Re: detecting from the browser – I like this, but instead of putting it in a cookie, put it in the user's profile if it isn't set there. Some authentication strategies (e.g. OpenID, LDAP, etc.) can have TZ information that can be used – in those cases, it shouldn't be set based on browser's timezone.
Ciao!