Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12554

Incorrect timestamps after re-importing a backup on a machine with a different timezone

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      When exporting data on a machine with timezone UTC+10 and importing it again on a machine with timezone UTC+2 all timestamps are off by 8 hours (note: they will show e.g. 4:30 pm on both machines regardless of the timezone).
      This causes issues with JIRA Agile data which is stored as unix timestamps and does not contain a timestamp by definition, those are imported correctly with the right offset.

      Steps to reproduce:

      1. Set timezone to UTC+10
      2. Export data
      3. Stop JIRA
      4. Set timezone to UTC+2
      5. Start JIRA
      6. Import data

      Symptoms

      • Agile charts do not list the correct issues, and the graphs are also incorrect.
      • Issue dates such as created, updated are also incorrect.

            [JSWSERVER-12554] Incorrect timestamps after re-importing a backup on a machine with a different timezone

            SET Analytics Bot made changes -
            Support reference count Original: 43 New: 42
            Oleksandr Tkachenko made changes -
            Component/s New: Data Center [ 47392 ]
            SET Analytics Bot made changes -
            UIS Original: 6 New: 3
            SET Analytics Bot made changes -
            UIS Original: 5 New: 6
            SET Analytics Bot made changes -
            UIS Original: 6 New: 5
            SET Analytics Bot made changes -
            Support reference count Original: 42 New: 43
            SET Analytics Bot made changes -
            UIS Original: 3 New: 6
            Jeff Curry made changes -
            Remote Link Original: This issue links to "RUM-3283 (Bulldog)" [ 467630 ] New: This issue links to "RUM-3283 (JIRA Server (Bulldog))" [ 467630 ]
            SET Analytics Bot made changes -
            Support reference count Original: 41 New: 42
            SET Analytics Bot made changes -
            Support reference count Original: 40 New: 41

              Unassigned Unassigned
              wkritzinger Wolfgang Kritzinger
              Affected customers:
              13 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated: