Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Upgrading from Jira 4.4.1 to Jira 4.4.5

Fr0zt
Contributor
September 14, 2018

Hello.

A couple of days ago I performed an upgrade from Jira 4.4.1 to Jira 4.4.5.

My Jira is using MyQSL 5.5.

I created the database with the following command (as referred in the documentation):

create database jiradb character set utf8;

(DOcumentation: create database jiradb character set utf8;).

 

When I run the Jira 4.4.5 Installer I get this message: "Upgrade Check List. Backup your external database: Your Jira database will be incompatible with your existing Jira Version..."

jira.png

 

In here I choose next and I was able to make the upgrade successfully.

 

I don't understand why did i got this message. Is this only a reminder to check database compatibility?

What does this mean?

 

 

1 answer

0 votes
Mohamed Riza
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 17, 2018

Hi @Fr0zt

These are checklist items. 

The first one, which you have quoted, asks you to backup the Jira database before upgrading. This is because during an upgrade, there installer makes changes to the database of Jira. However, in case you need to role back to the previous version of Jira, then you cannot use this database anymore because of the changes made. Therefore you will be a backed up copy to roll back. 

This is just a precautionary measure. We highly recommend this. 

Fr0zt
Contributor
September 17, 2018

I see.

So this doesn't necessarily means that my database is not compatible with my Jira, right?

Keri
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 25, 2018

You're correct.  The message is a little misleading - it's not that the database version or configuration which is incompatible - it's that after the upgrade, the data will have been upgrades and the data will be incompatible with the old version Jira. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events