-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
4
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? 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:
- Set timezone to UTC+10
- Export data
- Stop JIRA
- Set timezone to UTC+2
- Start JIRA
- 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.
- is detailed by
-
JRACLOUD-65305 Cloud import does not record entries timezone correctly (change items, issue created dates, etc.)
- Closed
- is related to
-
JRACLOUD-65305 Cloud import does not record entries timezone correctly (change items, issue created dates, etc.)
- Closed
-
JSWSERVER-12554 Incorrect timestamps after re-importing a backup on a machine with a different timezone
- Gathering Impact
-
JRACLOUD-26039 Verify the system timezone when an XML backup is restored
- Closed
- mentioned in
-
Page Loading...