Kanban backlog and Sprint goals are missing after upgrading JIRA

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

After JIRA is upgraded to version > 7.6 and above, Kanban backlog and Sprint goals features might be missing on the agile boards

Cause

The database was not upgraded during the upgrade to a supported version and as a result certain upgrade tasks did not run.

(info) This was noticed specifically on Oracle 11 database which is not supported starting from JIRA 7.0.1 and above, Oracle 12C must be used

Due to incompatibilities, certain upgrade tasks will not run and even though the upgrade might look successful from the User Interface Perspective, under the hood JIRA is still not fully upgraded.

Diagnosis

To verify, please check JIRA logs (atlassian-jira.log(.1 - 5) located under $JIRA_HOME/log for the following:

1) Search for the most recent ___ Upgrade History ________________________   section, it should look something like this:

        7.12.3#712001
              Time Performed                                : 2019-02-01 19:20:59.17
              Original Version                              : 7.4.5#74002
    
         7.4.5#74002
              Time Performed                                : 2017-10-27 21:12:10.533
              Original Version                              : 7.3.8#73011
    
         7.3.8#73011
              Time Performed                                : 2017-07-14 23:00:26.452
              Original Version                              : 7.2.7#72009
    
         7.2.7#72009
              Time Performed                                : 2017-01-13 21:12:32.05
              Original Version                              : 7.2.3#72005
    
         7.2.3#72005
              Time Performed                                : 2016-10-22 22:35:12.266
              Original Version                              : 7.0.10#70120

In the above example, if the target JIRA version was 7.12.3, then it looks like the upgrade was OK and something else is at play;

If 7.12.3 record is missing, but JIRA was supposedly upgraded to version 7.12.3 - then it means the upgrade was not successful

2) Check for any failed upgrade tasks like this:

2019-02-08 10:53:58,845 Caesium-1-3 ERROR [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [host,buildNumber=72001] failed

If you see anything like this – that means the upgrade has failed for some reason and you will need to redo it

3) Please check if the following dark features are not enabled in your JIRA:

com.atlassian.jira.agile.darkfeature.kanplan.enabled
com.atlassian.jira.agile.darkfeature.kanplan.epics.and.versions.enabled
com.atlassian.jira.agile.darkfeature.sprint.goal.enabled

If these features are not present in JIRA, that's also a good indication that a certain upgrade task did not run – these should have been added as part of the ugprade

Resolution

Please review the upgrade notes for the version of JIRA you're upgrading to and supported platforms, ensure all the requirements are met and repeat the upgrade.

For the upgrade notes and supported platform requirements please reference these resources:

Upgrade Notes - Notice you can change JIRA version to the one you're upgrading to on the right hand side of the page

Supported platforms

If absolutely certain that the upgrade was successful (no above listed symptoms) - please enable the above listed dark features and see if that resolves the issue. If it doesn't, please contact Technical Support for assistance




Last modified on Feb 22, 2019

Was this helpful?

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