500 page error when using project issue filter

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

Problem

After click on the Project issue filter (such as Assign to Me link), JIRA will throw 500 error page. It will happen if user click on the "Issues > Search for issues" menu as well.

The following will appears in the web browser:

1 2 3 4 5 6 7 8 9 Referer URL: <base-url>/browse/<project>/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils at com.atlassian.jira.components.query.DefaultSearcherService.getEditHtml(DefaultSearcherService.java:474) at com.atlassian.jira.components.query.DefaultSearcherService.getValueResults(DefaultSearcherService.java:259) at com.atlassian.jira.components.query.DefaultSearcherService.getSearchResults(DefaultSearcherService.java:180) at com.atlassian.jira.components.query.DefaultSearcherService.searchWithJql(DefaultSearcherService.java:174) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

Diagnosis

Environment

  • JIRA 6.3.15

Diagnostic Steps

  • Check if any bundled plugin jar file store at the installed-plugins/plugins folder via JIRA home directory.

Cause

There is a jar file overwrite the default bundled plugin version.

Solution

Resolution

Remove the bundled plugin jar file from the installed-plugins/plugins folder via JIRA home directory and restart JIRA to resolved the problem.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.