You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Team,
We are migrating jira projects from one server (half of the projects from other company) to our instance. We have taken temporary instance and load their data. They are in GMT-05:00) Toronto, we are on GMT-05:00) Chicago, Should we still setup the Set JVM timestamp to GMT to avoid time stamp differences ?
1. Exported their data on sbx environment (.zip file) : /data/atlassian/jira-data/export/(file: XXXX.zip)
2. Set JVM timestamp to GMT
3. Copy the attachments to here (/data/atlassian/jira-data/import/attachments/) before project import manually
4. Copy the avatars ( the path <jira-home>/data/avatars)
4. Imported the data into dev instance : /data/atlassian/jira-data/import/(file: XXX.zip)
Hi @Lakshmi S
I have imported data from other regions and have never had any issues with timestamps.
Whenever I have had to perform a major change like this, I have pre-tested the process on a staging copy of production first. In my experience every Jira migration has it's own unexpected events so a dry run is essential.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.