It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Software is currently unavailable. Edited

Hi all,

 

I've upgraded JIRA from 6.2 -> 6.4 -> 7.2 -> 7.4

6.4 was working fine, however upon upgrading to 7.2 the following error welcomed me on the main screen:

JIRA Software is currently unavailable. This might be because an upgrade task has failed to run or has not yet completed.

I've tried the solution below, it did find a plugin "HIPCHAT" which was deacativated, i activated it using the script provided. However the problem still persists.

https://confluence.atlassian.com/jirakb/jira-software-is-currently-unavailable-error-after-upgrading-to-jira-7-or-newer-794373743.html

Any suggestions where to look?

 

2 answers

1 accepted

Hi Dan,

Unfortunately you missed the critical path when doing the upgrade. JIRA Agile (separate plugin in 6.4) requires tasks that run in the JIRA Software 7.0 installer. They're removed from 7.1 and onward, so you must do an interim install at 7.0.

From JIRA Software 7.0 upgrade notes (pretty easy to miss):

If you're upgrading from an earlier version of JIRA and JIRA Agile, you need to upgrade to JIRA Software 7.0 before you upgrade to any later versions.
Use the upgrade path JIRA 5.1 OR EARLIER → JIRA 5.2 OR LATER → JIRA SOFTWARE 7.0 The intermediary upgrade version is necessary due to upgrade tasks that were removed in JIRA Software 7.0.0.


Hopefully you've done this on a test environment and you can just start fresh again and stop at 7.0 during your upgrade path. If you find yourself in this state on a production environment, I suggest contacting Support (support.atlassian.com) to see if they can help you push those migration steps through via SQL queries.

Thanks man I've contacted the support. I've realized what ive done wrong now.

Having suffered similar issues recently, ensure that when upgrading Jira Software ensure you apply each and every update in sequence. Don't skip any. I tried going from 7.3.1 to 7.4.2 the other day ... yup broke the product. Rolled back to a snapshot then applied each remaining 7.3.X update individually. 7.4.0 deprecates a key database directive that you have to fix by hand otherwise the product won't run. I then applied remaining 7.4.X patches and all appeared to be working fine.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

3,747 views 15 27
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you