-
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
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
JRACLOUD-26039 Verify the system timezone when an XML backup is restored
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JRACLOUD-66851] Incorrect timestamps after re-importing a backup on a machine with a different timezone
This issue is reported for cloud to cloud Jira migration whereas JRACLOUD-65305 is solution for server to cloud migration. How the workaround mentioned in JRACLOUD-65305 wouls suit for cloud to cloud migration. User does not control workaround given in there(changing timezone in server? on cloud). how this ticket is closed with JRACLOUD-65305.
Can you please explain?
The issue behavior changed and it has been detailed in JRACLOUD-65305.
Please see above bug ticket for details.
ranjith49, After moving to the new Cloud infrastructure this issue cannot possibly happen anymore in Cloud to Cloud migrations. Only in Server to Cloud migrations.