Cloud(latest version) to Server(latest version) - missing 'key' field in entities.xml

[Wiljan Hooijer]

When we make a cloud backup for server and try to upload it to our new installed server instance we get the error "missing 'key' field in entities.xml".

We tried the atlassian-xml-cleaner-0.1.jar but unfortunately no luck.

Also when you look at the line <Issue Id="" ...> there is no key field to be found in all the lines. Are we supposed to add these key fields and use the main key from each project to do so?

Please advise, thanks in advance.

[Wiljan Hooijer]

So i did what i mentioned in my previous post.

I added the keys to all the issue lines and this error didn't show up anymore. 

However i was greeted with the following error: 

This data appears to be from an older version of Jira. Please upgrade the data and try again. The current version of Jira is at build number '801001', but the supplied backup file was for build number '72002'.

Now i found on another forum post to do the following:

add this line to setenv.sh /.bat

set JVM_SUPPORT_RECOMMENDED_ARGS="-Djira.downgrade.allowed=true"

I ran the batch file again but it doesn't seem to work. 

However I'm going to try and restart the service/server and see what happens. 

[Wiljan Hooijer]

Adding the line to setenv.sh /bat didn't work however changing the build number in the entities.xml (OSPropertyString id="1" value="801001"/>) file did work now i'm able to to actually upload projects. 

But than I was greeted with some more errors:
The backup project 'projectname' requires custom field named 'Budget' with full key 'com.atlassian.jira.plugin.system.customfieldtypes:select'. In the current instance of Jira the plugin is at version '1.0', but this custom field was not installed in the backup data. You may want to create an XML backup with this version of the plugin installed. (* 20)

Another one to try and solve, hopefully this helps some other people who are having the same issues like me. 

[Miba]

@Wiljan Hooijer Did you find the solution?

I have the exactly the same issue!