-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When migrating JIRA to another server, if there are timezone inconsistencies between the two servers it can cause considerable problems with the new server that may not be discovered until problems have been introduced into the dataset. Please enhance JIRA to timestamp an XML backup and provide a warning during XML restore that the backup does not match the server time of the instance it is being imported into.
- Times stored in the database is based on the JIRA JVM user timezone
Workaround
In order to restore the times back to their last known working form, the below process can be used for the new server:
- Generate an XML backup from the previous server, or obtain the last-known working one and copy it to the new JIRA server.
- Schedule a downtime window.
- Stop the new JIRA server.
- Either:
- Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
- Change the System Time of the server that the JVM is running on (the JVM will default to that time).
- Start the new JIRA server.
- Import the XML backup from the previous server.
- Test JIRA.
If the server is unable to be rolled back, the below can be followed, however this is not the recommend method and may cause additional problems due to time inconsistencies.
- Schedule a downtime window.
- Export the XML backup.
- Stop JIRA.
- Either:
- Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
- Change the System Time of the server that the JVM is running on (the JVM will default to that time).
- Start JIRA.
- Import the XML backup.
- Test JIRA.
- causes
-
JSWSERVER-5433 Restoring Sprint data in a different server timezone broken
-
- Closed
-
- is related to
-
JSWSERVER-20247 Date Time field not preserved after removing JVM timezone argument
-
- Gathering Impact
-
- relates to
-
JRACLOUD-26039 Verify the system timezone when an XML backup is restored
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Thanks for taking the time to raise this issue.
Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.
I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.
Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com