Timezone in Russia causing Tempo to fail

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: None

      Summary

      There is currently an issue where it is not possible for Russian customers to log work via Tempo. Due to outdated timezone data on the system; attempting to log work with Tempo will result in an error page.

      Steps to Replicate

      Just grab a Russian instance and try logging work via Tempo.

      Expected Result

      Working hours logged.

      Current Result

      Error page shows when attempting to log work.

      Workaround (suggested by Tempo)

      One possible solution is to restart the JIRA instance with this option:
      "-Duser.timezone=Europe/Tallinn". That might however cause problems in the autumn as Tallinn respects Daylight Saving, whereas Moscow does not.

      • Change the system timezone to Tallinn. If user wants an immediate fix; this workaround can be fixed; but it should not be a permanent fix.

      A confirmed fix for this problem (instead of the Tallinn workaround) is to update the tzdate to at least tzdata2015a. This will need to be done by Atlassian Support. These pages includes more information: http://www.oracle.com/technetwork/java/javase/tzdata-versions-138805.html, http://www.oracle.com/us/technologies/java/tzupdater-readme-136440.html

      • Update to the latest tzdata. (Preferred workaround by Tempo)

      Notes

      Tempo raised a bug ticket regarding this at https://tempoplugin.jira.com/browse/TT-2211 . Tempo suggested to upgrade the timezone data. Do check the ticket out for more information.

      Couldn't link the HOT ticket for some reason....So here it is.

      https://ops.internal.atlassian.com/jira/browse/HOT-30183

        1. tempo.png
          tempo.png
          290 kB

              Assignee:
              Piotr Klimkowski (Inactive)
              Reporter:
              Vincent Chin (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: