Jira Issue Filter Macro throws Internal Server error and fails to load
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
Problem
While using the JIRA issue Filter Macro, it may error out with Internal Server Error
The following appears in the atlassian-confluence.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
2019-10-08 13:10:50,097 ERROR [https-jsse-nio-8091-exec-3] [adaptavist.tm4c.webfragments.TraceLinksCondition] shouldDisplay There was an exception in Jira while trying to retrieve trace links count
-- url: /display/TEST/Test | page: 77989999 | traceId: d1ca61a9ab79999 | userName: admin | referer: https://confluencetest/display/TEST/Test | action: viewpage
com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 404
at com.atlassian.applinks.core.auth.ApplicationLinksStringReturningResponseHandler.handle(ApplicationLinksStringReturningResponseHandler.java:16)
at com.atlassian.applinks.core.auth.ApplicationLinksStringReturningResponseHandler.handle(ApplicationLinksStringReturningResponseHandler.java:13)
at com.atlassian.applinks.oauth.auth.OAuthApplinksReturningResponseHandler.handle(OAuthApplinksReturningResponseHandler.java:48)
at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:134)
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:106)
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:131)
at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.executeAndReturn(ApplicationLinkRequestAdaptor.java:53)
at com.atlassian.applinks.oauth.auth.OAuthRequest.executeAndReturn(OAuthRequest.java:84)
at com.atlassian.applinks.core.auth.AbstractApplicationLinkRequest.execute(AbstractApplicationLinkRequest.java:114)
at com.adaptavist.tm4c.services.TM4JService.requestForJira(TM4JService.java:39)
at com.adaptavist.tm4c.services.TM4JService.get(TM4JService.java:26)
at com.adaptavist.tm4c.webfragments.TraceLinksCondition.shouldDisplay(TraceLinksCondition.java:42)Diagnosis
Environment
This problem was identified in Confluence 6.13.8
Confluence running with the following Adaptavist plugin:
1
2
3
4
5
6
7
8
<key>com.adaptavist.tm4c</key>
<name>Test Management for Confluence </name>
<version>1.1.3</version>
<vendor>Adaptavist</vendor>
<status>ENABLED</status>
<vendor-url>http://www.adaptavist.com/</vendor-url>
<framework-version>2</framework-version>
<bundled>User installed</bundled>Diagnostic Steps
Verify if you have the Test Management Reporting for Confluence plugin installed
Verify if you have the Test Management for JIRA plugin installed
Cause
The Test Management for Confluence (reporting) is causing the problem.
Solution
Workaround
Uninstall the plugin(s) as disabling it may not resolve the issue.
To uninstall, navigate to Manage Apps page in Confluence
Search for the add-on, click on it and then on the Uninstall button
Make sure that your application link between Confluence and JIRA is healthy
Resolution
There's no solution at the moment as the problem is caused by a third-party plugin (not bundled with Confluence installation). In case this add-on is required for your business, we should reach for Adaptavist support at:
Was this helpful?