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

How to deal with incompatible AddOns in JIRA 7 upgrade

Dirk Bromberg

Hi,

we plan to upgrade from JIRA 6 to 7 and the check tells us not all addons are compatible, for example the Agile Addon. How to deal with that Addons? (We don't use them right now). It's for example JIRA Agile and Bitbucket Importer Plugin for JIM. And there are some unknown once: Atlassian Hipchat Integration Plugin and Atlassian Universal Plugin Manager Self-Update Plugin and some more...

We tried a planin update with a lot dependency and class not found errors... and reverted the vm snapshot smile

What is the best way?

Thanks for ideas!

Accepted answers

Nic Brough -Adaptavist-

JIRA Agile is replaced by JIRA Software, so when you do the upgrade, upgrade to JIRA 7 Software, and that solves that problem.

The Atlassian ones you mention are also not a problem, the new version contains valid versions of them. The only dodgy one you've listed there is the Bitbucket importer. The worst case for that one is that it stops working for imports, it won't break anything else.

So there's not actually a lot there that will be a problem, if you use the right path (Go to JIRA Software, not Core)

All comments

Nic Brough -Adaptavist-

JIRA Agile is replaced by JIRA Software, so when you do the upgrade, upgrade to JIRA 7 Software, and that solves that problem.

Dirk Bromberg

Hm,

after a direct upgrade to software there are a lot of errors in log because of missing classes from plugins wich needs a upgrade for 7 for example the JIRA Toolkit Addon. And the JIRA only shows the oops an error occurred page. Is it a idea to deactivate the addons before upgrade and update them after upgrade?

Nic Brough -Adaptavist-

Yes and no. Most addons, yes, you can disable and update afterwards. But some have upgrade routines that aren't properly triggered by that, and you actually need them enabled. Very much depends on the versions in play. There's not a lot of them though, and you'll not have problems if you do the following: - With your old system, upgrade all the addons to the latest valid version - Disable all the "user installed" addons, except Agile and Service Desk if you have one or both of them - Perform the upgrade (to Software if you had Agile) - *Test it*, check logs etc - Re-enable the add-ons one at a time, and immediately upgrade them if there's a new version required for the new JIRA version - Test the addons are now working - Hand it back to the users Obviously, you should dry-run this all in a test system first.

Dirk Bromberg

Yea, Thanks a lot for this list. I'll try this. Is there a common way to avoid user access during maintenance? Maybe some JIRA builtin function? Otherwise I change the proxy before...

Dirk Bromberg

Thanks Nic for Supporting this. It finally helped to disabel all useraddons before and update enable after upgrade. There where unexpected errors on update, but after restart of jira it looks fine. Great!

Vinny_Petrillo

Hello Dirk,

Would you kindly update if your upgrade was successful by disabling add-ons? I am having a similar issue upgrading from 6.4 to 7. Thanks.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration