Boards fail to load with the error: "NoSuchMethodError" after upgrade to Jira v9.0 and above

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Summary

Accessing Boards or browsing Jira issues from the "Active Sprint" view on a project displays the following error in Jira UI:

1 java.lang.NoSuchMethodError: 'java.util.Collection com.atlassian.jira.issue.changehistory.ChangeHistoryManager.getPreviousIssueKeys(java.lang.Long)'

Environment

Jira v9.0.0 and above

Diagnosis

Reviewing the entire stack trace from the atlassian-jira.log, especially the caused by section reveals an error being thrown from a 3rd party add-on Subversion ALM on getLogEntriesByRepository call:

1 2 3 4 5 6 7 8 2022-09-15 09:52:03,165+0200 https-openssl-nio-443-exec-19 url: /rest/greenhopper/1.0/xboard/issue/details.json; user: xyz ERROR xyz 592x23478x1 /rest/greenhopper/1.0/xboard/issue/details.json [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: java.lang.NoSuchMethodError: 'java.util.Collection com.atlassian.jira.issue.changehistory.ChangeHistoryManager.getPreviousIssueKeys(java.lang.Long)' java.lang.RuntimeException: java.lang.NoSuchMethodError: 'java.util.Collection com.atlassian.jira.issue.changehistory.ChangeHistoryManager.getPreviousIssueKeys(java.lang.Long)' at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:69) Caused by: java.lang.NoSuchMethodError: 'java.util.Collection com.atlassian.jira.issue.changehistory.ChangeHistoryManager.getPreviousIssueKeys(java.lang.Long)' at com.kintosoft.svnwebclient.jira.SWCUtils.getLogEntriesByRepository(SWCUtils.java:891) at com.kintosoft.jira.plugin.ext.subversion.agiletabpanels.SubversionAgileTabPanelContext.getContextMap(SubversionAgileTabPanelContext.java:85) at com.atlassian.plugin.web.model.AbstractWebItem.getContextMap(AbstractWebItem.java:27)

Cause

The issue is due to the Subversion ALM add-on versionnot being compatible with Jira v9.0 and above. The compatible version of the add-on for Jira v9.0 and above is v9.4.0 You can check the version history here: subversion-alm/version-history

Solution

Update the Subversion ALM add-on version to 9.4.0 to make it compatible with Jira 9.0 and above. This should resolve the issue of accessing the Jira boards.

Updated on March 18, 2025

Still need help?

The Atlassian Community is here for you.