"Internal server error" when trying to browse Custom Fields

Sagi

When I try to access Custom Fields, I get an Internal server error (attached screenshot), and custom fields are not displayed.

This started after trying to add a new custom field.

Trying to figure this out for more than a week but with no luck so far.

Tried the resolution suggested on https://community.atlassian.com/t5/Jira-questions/Internal-server-error-when-open-Custom-Fields/qaq-p/936744 but the query failed.

Any ideas would be appreciated. 

 

Sagi

Issue resolved!

Duplicate fields were found and deleted directly from the database.

Xray View Test Execution Screen

Xray View Test Execution Screen This is the view operation screen for Test Execution issue type General NULL 0 customfield_11926
Xray View Test Execution Screen This is the view operation screen for Test Execution issue type General NULL 0 customfield_11926

Xray Default Test Execution Screen

Xray Default Test Execution Screen This is the default screen for the create/edit operations on Test Execution issues Test Execution Details NULL 1 customfield_11926
Xray Default Test Execution Screen This is the default screen for the create/edit operations on Test Execution issues Test Execution Details NULL 1 customfield_11926

My assumption is that something added the same field to the screen which is messing it up as there should never be duplicate fields in the same screen. From here we'll want to remove one. I'm opting that we remove the second entry as that looks to be the newer addition. From here you'll need to remove that entry. Instructions below as reference.

1. Backup Jira's database and get a XML backup of your Jira.
2. Shutdown Jira.

3. select * from fieldscreenlayoutitem where id = 13361;
   select * from fieldscreenlayoutitem where id = 13360;

   • First check for singular item

4. delete from fieldscreenlayoutitem where id = 13361;
   delete from fieldscreenlayoutitem where id = 13360;

5. select * from fieldscreen fs JOIN fieldscreentab fst ON fst.fieldscreen = fs.id JOIN fieldscreenlayoutitem fsl ON fsl.fieldscreentab = fst.id WHERE fs.name = 'Xray Default Test Execution Screen'
   select * from fieldscreen fs JOIN fieldscreentab fst ON fst.fieldscreen = fs.id JOIN fieldscreenlayoutitem fsl ON fsl.fieldscreentab = fst.id WHERE fs.name = 'Xray View Test Execution Screen';

   • You can check to see that entry is removed and there are no duplicates on the screens.
6. Start Jira.
7. Perform a Lock Jira and reindex.

This should help to return the Screen and Custom Field config back to normal operation.

Additionally, I want to note we have a Suggestion to remove the ability for Java API to creation this condition at JRASERVER-64998: Prevent the same custom field from being added to multiple screen tabs in JIRA's Java API.