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; } } }

upgrading from 8.13 to 10.3

Peter Stickney

I have been charged with migrating an existing 8.13.7 install hosted on RHEL 7 to a 10.3 install hosted on RHEL 9.

I haven't found much in the way of a plan for this, so I thought I would install 8.13.7 on my new server, import the data from the old server and then do in place upgrades on my new server, until I got to the desired version. Which would look something like this:

8.13.7 → 8.13.27 → 8.20.30 → 9.4.30 →9.12.29 → 10.3.13

Is that overkill?

I realize the docs for most of those versions isn't even online anymore, so I don't have know what hiccups to expect, or settings to tweak. Anyone have any more experience with something like this?

Accepted answers

Matteo Vecchiato

Hi @Peter Stickney ,

Welcome to Atlassian community.

Linux is always supported, so the steps you need to define are not dependent of SO.

The steps you need to define are mainly owed by the database supported version, you need to define the jumps based on database version.

Which current version of database you have?

Regards

Peter Stickney

Thanks @Matteo Vecchiato

I will be in the office tomorrow to look more closely at this. Sorry for asking more questions, I'm no expert in this software, but are you asking what version of database server, pgsql or mysql, we are running, or is there some schema version of the Jira database I have to find?

Tinker Fadoua

Welcome to the Atlassian Community @Peter Stickney !

I would have suggested 8.13.7 → 9.0.0 → 10.0.0 -> 10.3.13

Any reason you decided to go in the following order?

8.13.7 → 8.13.27 → 8.20.30 → 9.4.30 →9.12.29 → 10.3.13

Best,

Fadoua

All comments

Matteo Vecchiato

Hi @Peter Stickney ,

Welcome to Atlassian community.

Linux is always supported, so the steps you need to define are not dependent of SO.

The steps you need to define are mainly owed by the database supported version, you need to define the jumps based on database version.

Which current version of database you have?

Regards

Peter Stickney

Thanks @Matteo Vecchiato

Matteo Vecchiato

Yes, only Database server and version.

Tinker Fadoua

Welcome to the Atlassian Community @Peter Stickney !

I would have suggested 8.13.7 → 9.0.0 → 10.0.0 -> 10.3.13

Any reason you decided to go in the following order?

8.13.7 → 8.13.27 → 8.20.30 → 9.4.30 →9.12.29 → 10.3.13

Best,

Fadoua

Peter Stickney

@Tinker Fadoua from the docs I couldn't determine a logical upgrade path, so I just picked every LTS version. If yours is a supported path, I'd do that for sure, thanks for the suggestion.

Tinker Fadoua

Check the following for any manual upgrade:

https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-manual-938846951.html

I learned long time ago that when upgrading from a major version to another one, always upgrade to X.0.0 because that's the version that has the major changes then you can upgrade to X.y.z