Visiting the Custom Field page results in a 404 error page
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
Problem
When clicking on Custom Fields in Jira Administration, you get a 404 error message, stating "Oops, you've found a dead link".
There are no relevant error messages in the Jira application logs
Disabling "Enable HTML in custom field descriptions and list item values" from General Configuration does not resolve the problem
The problem persists regardless of the presence of a reverse proxy or not
Diagnosis
In Jira 7.11, a new screen was introduced for custom fields - see https://jira.atlassian.com/browse/JRASERVER-27957 for more details. The routing to the new screen is controlled through an action in $jira-install/atlassian-jira/WEB-INF/classes/actions.xml.
The feature is controlled via a feature flag, which is turned on by default. Turning the feature flag off is a useful diagnostic step:
Browse to
<your-jira-url>/secure/SiteDarkFeatures!default.jspaAdd an entry for
jira.customfields.paginated.ui.disabledVisit the custom fields page
If the custom fields page now displays correctly, proceed to the "Cause" section.
Cause
The files that control the new appearance aren't in line with those provided by a default installation. The files used are:
$jira-install/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/admin/customfields/ViewCustomFields.class
$jira-install/atlassian-jira/WEB-INF/classes/actions.xml
Download a copy of Jira, matching the current version you've got (as a zip or tarball) and compare the contents of those files. If they are different, proceed to the resolution.
Resolution
Replace the files in your current installation with those from the zip or tarball:
Shut down Jira, and backup the files to be changed
Delete the original files
Copy the files from the tarball to the original location, making sure to match the permissions the original files
Start Jira
Remove the feature flag from
<your-jira-url>/secure/SiteDarkFeatures!default.jspa
Was this helpful?