Jira Issues Macro in Confluence does not show Table or default columns
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
The Jira Issues Macro in Confluence does not allow the Table option to be created or Columns to display selection after upgrading to Jira 8.13.x.
Environment
Jira 8.13.10
Diagnosis
The user has permissions to browse the issues in the project.
The macro Table cannot be created, however Single issue or Total issue count macros are working properly.
The following errors are found in the application logs:
atlassian-confluence.log:
1
2
3
4
5
6
7
[extra.jira.columns.DefaultJiraIssuesColumnManager] getColumnsInfoFromJira Failed to fetch Jira fields:
...
Caused by: java.lang.RuntimeException: com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 500
at com.atlassian.confluence.extra.jira.columns.DefaultJiraIssuesColumnManager$CustomFieldsCacheLoader.load(DefaultJiraIssuesColumnManager.java:164)
at com.atlassian.confluence.extra.jira.columns.DefaultJiraIssuesColumnManager$CustomFieldsCacheLoader.load(DefaultJiraIssuesColumnManager.java:152)
at com.atlassian.cache.ehcache.wrapper.ValueProcessorAtlassianCacheLoaderDecorator.load(ValueProcessorAtlassianCacheLoaderDecorator.java:26)
at com.atlassian.cache.ehcache.LoadingCache.getFromLoader(LoadingCache.java:174)
atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
/rest/api/2/field [c.a.j.rest.exception.ExceptionInterceptor] Returning internal server error in response
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor3454.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker.lambda$_dispatch$0(DispatchProviderHelper.java:181)
...
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoSuchFieldError: FIELD_NON_BROWSE_PROJECTS_ACCESS
at
Caused by: java.lang.NoSuchFieldError: FIELD_NON_BROWSE_PROJECTS_ACCESS
at com.atlassian.jira.rest.v2.issue.FieldResource.getFields(FieldResource.java:97)
An SSO filter may also be found in the stacktrace:
1
com.resolution.atlasplugins.samlsso.servlet.RedirectToSsoFilter.doFilter
Cause
The root cause is not yet determined but may be related to the SAML Single Sign On (Jira SSO) Jira SAML SSO app or broken application links.
Solution
Attempt to disable the SSO and check if the gadget can be added.
Upgrading Jira to a later version (e.g. 8.13.x) has resolved the issue in some situations.
Was this helpful?