When importing an XML backup into a new JIRA instance, I get the errors below. How can bypass this error?
FYI: The source JIRA version is (v6.4.4) and the target JIRA version is (v6.4.5)
There are some plugins that have been known to cause issues. Stripping out the information from these plugins should allow the XML to import correctly. Take a look at our documentation for an easy way to strip out the problematic information. After removing the information you can then add the plugins back in later.
Try installing the Kepler custom fields addon in the target JIRA and retrying the import.
I've run into this error a number of times, and it's not just the Kepler ones that do it - it's often worth making sure you have the same addons installed in the target (compatible versions of course) as you do in the source JIRA when you are upgrading. Just the presence of the addon - so far, I've not seen one that needs configuration or other work, it's enough to make sure it is there.
Note that this is a bit of a long-shot. It's worth a try, but if it doesn't help, then don't waste any time trying to debug it further - follow Brian's advice as soon as it fails.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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