Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      My company has employees in different time zones, but since you can only
      configure Java to use one timezone, we can only make one group of users see the
      "right" time from hudson.

      You can detect the timezone from Javascript
      (http://onlineaspect.com/2007/06/08/auto-detect-a-time-zone-with-javascript/),
      so I suggest the following approach to using a user's timezone:
      Detect the browser's timezone on the first page load
      Set a cookie with the timezone in it
      On subsequent page view, use the timezone stored in the cookie. Fall back to the
      system time zone.

        Attachments

          Issue Links

            Activity

            Hide
            docwhat Christian Höltje added a comment -

            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!

            Show
            docwhat Christian Höltje added a comment - 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!
            Hide
            mistercaste Matteo Castellarin added a comment -

            +1
            Having the timezone (e.g. UTC) in the shown time would be a really great feature!

            Show
            mistercaste Matteo Castellarin added a comment - +1 Having the timezone (e.g. UTC) in the shown time would be a really great feature!

              People

              • Assignee:
                Unassigned
                Reporter:
                candrews candrews
              • Votes:
                62 Vote for this issue
                Watchers:
                39 Start watching this issue

                Dates

                • Created:
                  Updated: