Jira Service Management customer portal details section appears blank for all issues
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
The Jira Service Management customer portal details section appears blank for all issues.
Diagnosis
Errors similar to the following ones are shown in the atlassian-jira.log
192.168.1.4,10.0.0.61 /rest/analytics_stj/1.0/sd/table/stjvalues/issueKey/XXXX-12345 [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: service proxy has been destroyed
org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:101)
at org.eclipse.gemini.blueprint.service.importer.support.internal.support.RetryTemplate.execute(RetryTemplate.java:81)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.lookupService(ServiceDynamicInterceptor.java:427)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.getTarget(ServiceDynamicInterceptor.java:400)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:137)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:137)
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
at com.sun.proxy.$Proxy4120.getInstance(Unknown Source)
at com.atlassian.servicedesk.internal.user.UserFactoryOldImpl.lambda$wrap$0(UserFactoryOldImpl.java:84)
at io.atlassian.fugue.Option.map(Option.java:259)
at com.atlassian.servicedesk.internal.user.UserFactoryOldImpl.wrap(UserFactoryOldImpl.java:84)
at com.atlassian.servicedesk.internal.user.permission.ServiceDeskPermissionServiceOldImpl.isCustomer(ServiceDeskPermissionServiceOldImpl.java:109)
at com.atlassian.servicedesk.internal.user.permission.ServiceDeskPermissionServiceImpl.isCustomer(ServiceDeskPermissionServiceImpl.java:41)
at de.stagil.jira.tablefield.servicedesk.ServiceDeskCaller.hasPermission(ServiceDeskCaller.java:56)
at de.stagil.jira.tablefield.rest.SDTable.hasPermission(SDTable.java:259)
at de.stagil.jira.tablefield.rest.SDTable.getSOJValues(SDTable.java:158)
...
Cause
This issue is caused by the 3rd party app STAGIL Tables and Checklists for Jira as we can see classes from the de.stagil.jira.tablefield.rest package in the stack trace.
It is known that version 2.6.7 has a problem that can result in this behavior.
Solution
Upgrade to the latest version (2.6.8 or higher) of the plugin STAGIL Tables and Checklists for Jira or contact the app support if the upgrade doesn't fix the issue.