The import requires the versions to be the same.
However, 6.3 and 6.4 are quite similar, so you could try hacking the "build number" in the xml export (use a plain text editor to do that) and then try the import. It should work. (If it doesn't, then the answer becomes "no, you need to upgrade the data, by going through a dev install/upgrade)
No, the project import is fairly complicated, so it has never been made to support multiple versions. And for once I would disagree w/ Nic, here; I would definitely not recommend hacking the version number in the data to try to accomplish this. If we were talking a small bump like 6.4.10 to 6.4.12, I would say you have a good chance, but enough changes between version 6.3.x and 6.4.x that I wouldn't risk it.
The standard answer here is that you should create a temporary copy of JIRA at the target version, do a full system import there (which will upgrade the entire scheme), and then export from there to get an export at the desired version.
Yes, we know that this isn't a good answer for administrators and needs to be improved, but it is the safest way that you currently have available to you.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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