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

What can get wrong after Jira upgrade?

Rumceisz

Hi All,

what are those features, settings, etc in Jira what you would first check after upgrade?

We have upgraded Confluence for a couple of weeks ago and our users even today keep find errors, bugs which were resulted in the upgrade.

By the way, in the end we will- or our users - find these errors, but it should be avoided:)

We upgare from 4.3.4 to 5.1

Thanks in advance!

Rumi

Accepted answers

Jobin Kuruvilla [Adaptavist]

Mostly, the things that can wrong are the plugins and customizations you have done on JIRA files.

For plugins, you can use the JIRA Upgrade check to see if they are compatible. For all other customizations, it is your responsibility to test before you do it in Production.

Even for plugins, testing is desired although the upgrade check might give you an indication of whether it would work or not.

No easy way I am afraid!

All comments

Jobin Kuruvilla [Adaptavist]

Mostly, the things that can wrong are the plugins and customizations you have done on JIRA files.

For plugins, you can use the JIRA Upgrade check to see if they are compatible. For all other customizations, it is your responsibility to test before you do it in Production.

Even for plugins, testing is desired although the upgrade check might give you an indication of whether it would work or not.

No easy way I am afraid!

Rumceisz

Hi Jobin,

many thanks for the rapid response.

Where can I find this JIRA Upgrade check?

Jobin Kuruvilla [Adaptavist]

Administration > Plugins > JIRA Update Check. I think in earlier versions, it was part of UPM. There was tab like "Install Plugins"

Ellen Feaheny [

Hi @rumi

I think you answered your question in your question.

> We have upgraded Confluence for a couple of weeks ago and our users even today keep find errors, bugs which were resulted in the upgrade.

Validation of the staging upgrade first is core! (which also touches on the plugin issues the @jobin refers to).

Couple other ideas:

In particular for 4.X > 5.X, the APIs changed massively - and affected alot of plugins. These days, most of the plugins have caught up and you can upgrade. But assume nothing - verify!
This document is your friend - get it, understand it, realize it for yourself and users: https://confluence.atlassian.com/display/JIRA/JIRA+Release+Summary
Further, in the case of versions you cite, there are alot UX/UI changes between those. Admin and user side.

Be aware - since if you do not know, you will not be able to help your users when them come knocking at your door, post upgrade, complaining at you, one by one. Not fun.So be ready - or get them onboard before cutting over in a pilot.
If you have a large user community - enlist people into Atlassian University to get them up to speed faster. http://www.atlassian.com/software/university/overview

BTW - massive changes (good ones) in GreenHopper too - so this is also your friend. https://confluence.atlassian.com/display/GH/GreenHopper+Release+Notes

Have fun!

Ellen

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

upgrade

error