nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrating from JIRA 4.1 on Windows to JIRA 4.4 on Linux

Dana Bentley

We have recently joined with another company, and we're trying to add our project information from an instance of JIRA 4.1.2 #531 (running on Windows Server 2008) to JIRA 4.4 (running on Linux). I have a duplicate of the 4.4 running, and am trying to import the 4.1 XML file to create a new version of our database, but I cannot get past the file selection on the import screen due to the older file. What steps do I need to follow outside of regular import or backup procedures to manage this? All the documentation I have gone through appears to be for either a server change or an upgrade from scratch, but not for a migration of an older version of JIRA on one OS to a newer existing version (with different projects) on another.

Accepted answers

Dana Bentley

I've decided after reviewing the documentation to go the extra step and upgrade our instance of JIRA before exporting.

All comments

Nic Brough -Adaptavist-

I've done stuff like this loads of times - moving OS, database and server all at the same time more than once (scary, but it does work if you plan it properly)

You should be able to import that XML irrespective of what you're changing, so to try to get you moving, could you explain what you mean? For example, your question "what steps do I need to follow" has a simple answer - "import the xml". I think the key thing we need more detail on is what "but I cannot get past the file selection on the import screen due to the older file"? What error are you getting? What is it telling you? When you click import file, what are you putting in the box for the file name and have you made sure your new Jira server can see it and read it? And so on...

Gaston Gaston

I agree with Nic, we need more info in order to help you.

But, my advise to you, in order to start this process; is to get your current Jira env (On your Win Serv.) as the same version of the Linux env. Ergo, do this process in two separated phases:

a. Upgrade your Jira instance to the final version (Win env. version = Linux env. version).

(From that point on, there are several ways to accomplish your task, but every suggestion I can make has questions that need to be answered in order to give you the most accurated advice.)

b. Perform your platform migration.

TothJ

I recently upgraded our Jira 3.9.1 (linux) to Jira 4.3.4 (win) without any problems, just exported to xml, and imported in the new installation. An error message about "but I cannot get past the file selection on the import screen due to the older file" would be helpful. Also, this maked me wonder: " to a newer existing version (with different projects)" - different projects? existing version? you try to make 2 diffent versions to be one?

Dana Bentley

Using the Import Project in the Administration menu, I enter the file name of the xml backup for import. I receive the 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 '620', but the supplied backup file was for build number '531'.

I think that the update of the old data before trying to import it into the new instance is the way I'm going to have to go.There are already projects existing from the other company in their newer instance of JIRA, so I'm thinking that a restore isn't going to work.

Dana Bentley

I've decided after reviewing the documentation to go the extra step and upgrade our instance of JIRA before exporting.