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

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

The user is presented with the following error in the UI:

"JIRA Agile is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed.
Please contact your system administrator if you continue to see this message"

Diagnosis

  • Search the JIRA logs for JIRA Agile Run History
  • Check the history for any to see if there is any downgrade in JIRA versions. 
    Example:

    *********************************************************************************
    Atlassian GreenHopper v6.7.2 #a38ba3000d32f3b8 built 2015-05-21T05:04:26.273+02:00 - plugin starting...
    *********************************************************************************
    2015-10-19 19:19:35,262 ThreadPoolAsyncTaskExecutor::Thread 11 INFO      [greenhopper.service.logging.LogSupport] 
    JIRA Agile Run History
    	JIRA Agile v6.3.13.1 (a73d75f118867c66) started at 25 Aug 2014 11:19
    	JIRA Agile v6.5.0 (2f1369fa8b790f29) started at 25 Aug 2014 11:22
    	JIRA Agile v6.7.2 (a38ba3000d32f3b8) started at 26 May 2015 07:25
    	JIRA Agile v6.7.11 (71a5197f0180dc1d) started at 19 Oct 2015 11:51
    	*JIRA Agile v6.7.2 (a38ba3000d32f3b8) started at 19 Oct 2015 07:19
  • In the above example you will notice that JIRA Agile has been downgraded from JIRA Agile v6.7.11 to v6.7.2

Cause

It is not possible in JIRA to downgrade JIRA Agile versions from a newer version to an older version. Doing so will break your JIRA Agile

Alternative Cause

 Database is corrupted, either by not having all permissions to access the database, or because of the collation. For more details: Installing JIRA Agile gives Error message "JIRA Agile is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed"

 

Resolution

This resolution is only for the first cause. For the alternative cause please check the KB linked on the cause itself.

Upgrade JIRA Agile back to at least the latest upgraded version from the JIRA Agile Run History. From the above example provided, user will have to upgrade to at least JIRA Agile v6.7.11 in order to resolve the issue.


JIRA Agile versions can be downloaded from this page:https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira/versions. If the problem persists after the upgrade, then please provide an updated support zip to Atlassian Support.

Last modified on Apr 7, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.