Upgrading JIRA using rapid method

[Surbhi_Kaushik]

Hi Team,

We have been using JIRA v7.2.2 and planning to upgrade it v7.12.1. We have upgraded our test environment to v7.12.1 taking latest DB backup from Production environment.

Now, our management is deciding to use the QA as Production only and for delta changes they want these changes to be replicated from Production DB.

However, I am not sure whether there is any possible method to have data copied from older version to new version. Any help would be highly appreciated.

[Amith Mathur {Appfire}]

Hi @Surbhi_Kaushik , 

Unfortunately, you will not be able to bring the contents from your JIRA v7.2.2. 

If everything is tested in the v7.12.1, then we would suggest you to perform the JIRA upgrade for your production environment. 

Thanks,
Amith Mathur

[Surbhi_Kaushik]

Thanks for response @Amith Mathur {Appfire} : So, there is no possibility from Database end to identify the delta transactions ( for the duration when the backup was taken from Production till the date users have last used production instance) and then copy it to upgraded JIRA instance. 

I just want to understand the reason due to which such type of transactions can't be applied. Any example would be of great help.

[Dave Theodore [Coyote Creek Consulting]]

There is not, unfortunately. You will need to perform the upgrade all at once.  There is no way to sync over only the delta of database data.  You can use a tool like rsync to catch up the attachment changes, though.

[Surbhi_Kaushik]

Thanks @Dave Theodore [Coyote Creek Consulting] : Yeah, rsync can be used for server side changes. 

What if I want to take complete copy of DB from previous JIRA v7.2.2 and point JIRA v7.12.1 to this new copy of DB.

Also, XML backup is another option. We have used it to migrate from MySQL to MS database earlier. 

[Nic Brough -Adaptavist-]

The best way to upgrade is to take a 7.2.2 and upgrade as per the documentation. 

You could take a copy of the database and point a 7.12.1 installation at it, and it should detect the mismatch and upgrade the data for you, BUT this is not the supported way to do it, and often fails, especially when you have apps installed.

Importing from XML is a third option, but is even less reliable (and slower) than pointing a new install at an old database.