How do I fix "Internal server error" when trying to browse Custom Fields?

[Adrian Stewart]

We use Cloud Jira and I fear I have caused an issue by creating a custom field, assigning it to a screen and then assigning again in the actual screen, thereby causing a duplicate entry in some database table.

I understand others have edited the database tables but what can we do if it's Cloud Jira to fix this?

Jira Info:

Version: 8.4.0

Build Number: 804

Build Date: Mon Sep 09 00:00:00 UTC 2019

Build Revision: a071452da0cda52aa7f8d05a411ca434beaf3c1f

Stack trace below trying to delete the offending screen:

Technical details

Log's referral number: 617f84b4-56bb-418d-ac4e-37577727f07e

Cause

Referer URL: https://issues.corp.rapid7.com/secure/admin/ViewDeleteFieldScreen.jspa?id=15560

Technical details

Log's referral number: fb7ffb60-bbd5-4f7d-9003-27d13b9c00e5

Cause

Referer URL: https://issues.corp.rapid7.com/secure/admin/ViewDeleteFieldScreen.jspa?id=15560

java.lang.NullPointerException

java.lang.NullPointerException
	at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenStore.removeFieldScreenLayoutItems(DefaultFieldScreenStore.java:121) [classes/:?]
	at com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.removeFieldScreenLayoutItems(CachingFieldScreenStore.java:136) [classes/:?]
	at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenManager.removeFieldScreenLayoutItems(DefaultFieldScreenManager.java:99) [classes/:?]
	at com.atlassian.jira.issue.fields.screen.FieldScreenImpl.remove(FieldScreenImpl.java:180) [classes/:?]
	at com.atlassian.jira.web.action.admin.issuefields.screens.ViewFieldScreens.doDeleteFieldScreen(ViewFieldScreens.java:104) [classes/:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_202]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_202]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_202]
	at java.lang.reflect.Method.invoke(Method.java:498) [?:1.8.0_202]
	at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) [webwork-1.4-atlassian-30.jar:?]
	at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) [webwork-1.4-atlassian-30.jar:?]
	at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:438) [webwork-1.4-atlassian-30.jar:?]
	at webwork.action.ActionSupport.execute(ActionSupport.java:157) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-8.4.0.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:138) [classes/:?]

[John Funk]

Hi Adrian - I would start by making sure you have configured the custom field to attach it to either a project (or projects) and/or an issue type (or issue types). If that doesn't help, you probably want to submit a support ticket to Atlassian so they could remove any obstacles.