Requirement: JIRA 3.3 to JIRA 7.x. But during upgrate i figured out that it is not possible to directly switch from 3.x to 7.x. First need to upgrade to JIRA 4.4.5 and then to JIRA 7.x.
I took back up of xml as zip file and trying to import to JIRA 4.4.5 (TRIAL version) and faced JVM memory out of space issue. Later in services i updated to 512 as max. Then tried to import and it has completed till 11% and failed with unknown error.
You'll want to look at the atlassian-jira.log and find out why it's failing. If you have 512MB for the heap that is going to be too low as the default heap size is over 700MB. I would take a look at the logs and see what the error is when it fails. Regardless, depending on the number of issues, custom fields etc., use the JIRA Sizing Guide to determine the correct amount of heap to add to your system and retry.
If increasing the heap does not help, paste the snippet of code where the failure is and I'll see what we can find.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs