Jira Navigation to System Field page gives 404 Page not found error
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
Observed 404 error while accessing System Fields page navigated from System -> Issues -> System fields
System fields page functionality is introduced in 8.16. After migration from 8.13 to 8.20, observed 404 errors while accessing System fields.
Environment
8.20.x
Diagnosis
The initial log analysis shows below the error message in atlassian-jira.log:
1
http-nio-8080-exec-204 ERROR XXXXXXXX 342x306034x1 2k4kok 103.205.152.154,172.17.128.167 /secure/admin/ViewSystemFields.jspa [c.a.j.web.dispatcher.JiraWebworkActionDispatcher] Exception thrown from action 'ViewSystemFields', returning 404 WebworkConfigurationNotFoundException {class=class webwork.config.XMLActionConfiguration, message='No such view mapping', name='ViewSystemFields.actionRoles.actionRoles'}Cause
Cause 1: Some plugins were disabled:
This issue can be caused due to disabled plugins. To confirm if any of the plugins are disabled, you can run the following SELECT SQL query in the Jira database:
1
SELECT * FROM pluginstate where pluginenabled = 'false'Cause 2: Required files do not exist under the JIRA installation directory:
Navigate to $JIRA_INSTALL directory and confirm if the below files are present:
1
2
3
4
./WEB-INF/classes/com/atlassian/jira/web/action/admin/systemfields/ViewSystemFields$FieldDTO$Builder.class
./WEB-INF/classes/com/atlassian/jira/web/action/admin/systemfields/ViewSystemFields$FieldDTO.class
./WEB-INF/classes/com/atlassian/jira/web/action/admin/systemfields/ViewSystemFields$1.class
./WEB-INF/classes/com/atlassian/jira/web/action/admin/systemfields/ViewSystemFields.classCause 3: Check the SiteDarkFeatures
Navigate to /secure/SiteDarkFeatures!default.jspa add entry: jira.customfields.paginated.ui.disabled and refresh custom fields page.
If the System field page loads -> Meaning there is something wrong with the design files, we can reinstall Jira.
If the System field page won't load -> Meaning the problem is rather "one level above" let's move to Cause 4.
Cause 4: Check actions.xml
Look for the actions.xml via $JIRA_INSTALL/WEB-INF/classes/ directory and confirm the below snippet exists:
1
2
3
4
5
6
7
<action name="admin.systemfields.ViewSystemFields" alias="ViewSystemFields" roles-required="admin">
<view name="success" type="soy">:viewsystemfields/JIRA.Templates.Admin.Systemfields.systemfieldsPage</view>
</action>
<action name="admin.systemfields.ConfigureField" alias="ConfigureField" roles-required="admin">
<view name="success" type="soy">:action-soy-templates/JIRA.Templates.Admin.ConfigureField.main</view>
<view name="error" type="soy">:action-soy-templates/JIRA.Templates.Admin.ConfigureField.fieldNotFound</view>
</action>Solution
Solution 1:
If incase of pluginenabled table is mentioned as False, you can follow the steps to refresh the plugin cache:
Stop JIRA
Delete the content of $JIRA_INSTALL/work directory
Delete the content of $JIRA_HOME/plugins/.bundled-plugins directory
Delete the content of $JIRA_HOME/plugins/.osgi-plugins directory
Run this query to enable the disabled plugin:
1UPDATE pluginstate SET pluginenabled = 'true' WHERE pluginkey='<pluginkey from query above>';Note that you need to replace XXXX with plugin key returned from the select query.
Run the next query to make sure no plugin is disabled
1SELECT * FROM pluginstate where pluginenabled = 'false';Start JIRA and check again if the same error happens in your latest logs.
Solution 2:
If the files are not present then need to find out the reason and confirm the installation was successfully completed. Please refer to the next cause.
Solution 4:
If no actions are found for ViewSystemFields and ConfigureField, please update the existing actions.xml from the working environment to get this working. You may restart JIRA after the update.
Was this helpful?