HI everyone. I'm seeing multiple postings on this topic, but nothing about Jira7 and the basic question of "Why a very minor revision number change is preventing me from migrating off Cloud hosting"
The message I'm getting is:
Failed to start JIRA due to a build number inconsistency.
The data present in your database is newer than the version of JIRA you are trying to startup.
Please use the correct version of JIRA. You are running: 7.0.5#70114-
I downloaded V7.0.5 off Atlassian 2 days ago, and I did my data import within the same day. If Atlassian is constantly upgrading the cloud service with new build numbers, how can we ever complete a migration off it, if the newbuilds are not available for download?
The implied question is, where do I get JIRA build 71001 ?
So after a day and a half of back and forth with Atlassian, I finally got them to admit that "oh, yeah, we had a problem with cloud hosting that might have impacted exports. Run a new export, and try to import that." - I did this, and the import was successful. Note the build numbers didn't change, so this was purely a misconfiguration on their end. I'm glad they did own up to the problem, but would have been happier if it hadn't taken several back and forths until the problem was addressed.
That build number does not exist in the XML files except as realistic values as part of the rest of the data. The closest thing I've found is this: entities.xml: <OSCurrentStep id="71001" entryId="55646" stepId="4" actionId="0" owner="" startDate="2015-05-04 22:41:49.067" status="null"/> But that is in the middle of whole slew of OSCurrentStep entries. I can't just change one in the middle of hundreds.
Seems if I do one now... JIRA Software v7.0.5#70114 and Ondemand 7.1.0-OD-04-012#71001 I have no issues.. other than to accept that the versions don't match I would therefore update your local server install to the latest - then are-attempt your migration - Would seem to be simplest... if ofcourse your plugins allow you to. I don't have the time now, but will install an older JIRA and perform the same where the build number is different.
I didn't need to update the entities.xml - just installed a JiRA software license at he point of import. Complained about the versions being different and opted to carry on. My local JIRA was a fresh download and the database was empty. The whole process took less than hour I can happily screen share this evening as I'm with clients all day.
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