Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-656

When using Mexico Default Timezone DateTime fields are converted 1 hour ahead on Excel and GSheets Export

XMLWordPrintable

    • Severity 2 - Major
    • 1

      Issue Summary

      When using Mexico Default Timezone DateTime fields are converted 1 hour ahead on Excel and GSheets Export.

      This may be caused due to Daylight Saving time. However, the Mexican Government has declared that Mexico will only have one Standard time from 2023, and the time will not be adjusted as per the DST adjustment.

      Time-related data are getting affected, thus impacting the business.

      Steps to Reproduce

      1. Set the Atlassian Account timezone preference - or Default user time zone on Jira General Configuration - to (Mexico/Mexico City GMT-6) 
      2. Go to the 'Advanced Issue search' page
      3. Click on the Excel Icon (Open in Microsoft Excel)
      4. Check for Date/Time fields.

      Screen recording of the problem experienced: Incorrect Time on Excel Export

      Expected Results

      As Mexico eliminated the DST (Daylight saving time), no automatic changes should occur to the time set in the date/time fields when exporting and reviewing data via Excel.

      Actual Results

      When using the Mexico timezone, if there is a field filled in with April 03, 2023, 09:00 AM in JIRA, after exporting to Excel the field is converted to April 03, 2023, 10:00 AM, for example.

      Workaround

      • Using a different Time zone with a similar GMT in which Daylight Saving rules are not applied (for example, Guatemala GMT-6).
      • Exporting Issue through other native option (eg CSV) since it's unaffected by the bug.

        1. image-2023-05-12-14-32-21-903.png
          image-2023-05-12-14-32-21-903.png
          297 kB

            [API-656] When using Mexico Default Timezone DateTime fields are converted 1 hour ahead on Excel and GSheets Export

            Vitalii Saienko (Inactive) added a comment -

            Hello,

            Great news! We've been able to identify the root cause and have already fixed the underline issue. Please give it another try and let me know if it works for you now.

            Vitalii Saienko (Inactive) added a comment - Hello, Great news! We've been able to identify the root cause and have already fixed the underline issue. Please give it another try and let me know if it works for you now.

            Hector Eduardo Calzada Tenorio added a comment -

            Hi Vitalii,

            We will be waiting for the ETA that you share. Thank you for your updates.

            Hector Eduardo Calzada Tenorio added a comment - Hi Vitalii, We will be waiting for the ETA that you share. Thank you for your updates.

            Vitalii Saienko (Inactive) added a comment -

            We are looking into this issue and trying to identify the root cause. Once we find it, we will provide ETA for the fix.

            Vitalii Saienko (Inactive) added a comment - We are looking into this issue and trying to identify the root cause. Once we find it, we will provide ETA for the fix.

            Jiayi Litten added a comment -

            Hi everyone,

            Thanks for your patience on this, we released a JDK version bump to fix the timezone bug and it should be available for everyone now. If you still experience the error/issue after that, please comment here to let us know the specific case.

            Thanks

            Atlassian engineering.

            Jiayi Litten added a comment - Hi everyone, Thanks for your patience on this, we released a JDK version bump to fix the timezone bug and it should be available for everyone now. If you still experience the error/issue after that, please comment here to let us know the specific case. Thanks Atlassian engineering.

              ac1d9a6a7e17 Mykyta Koptsov (Inactive)
              701d8e7c44be Cassio Castilho
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: