nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to find and link JIRA ticket

Azraai Baharin

1. When adding JIRA macro, and trying to search for ticket, it returns "Received the following HTTP error code from the server: 200"

2. When adding a JIRA link, it gets converted to the JIRA macro, upon saving the updated page, the JIRA link is unable to display the details but instead displays the text: "java.io.IOException: Error on line 78: The entity name must immediately follow the '&' in the entity reference."

3. The following error is found in atlassian-confluence.log:

Caused by: java.io.IOException: Error on line 78: The entity name must immediately follow the '&' in the entity reference.
at com.atlassian.confluence.extra.jira.request.JiraChannelResponseHandler.getChannelElement(JiraChannelResponseHandler.java:48)
at com.atlassian.confluence.extra.jira.JiraIssuesManager$ByteStreamBasedSupplier.get(JiraIssuesManager.java:138)

4. Versions:
Confluence 7.6.2
Jira v8.8.0

5. The application links status both in JIRA and Confluence are "CONNECTED" with the outgoing and incoming connections set as "OAuth (impersonation)".

6. Same display is observed if using other user with the same permissions.

Accepted answers

All comments

Jan-Peter Rusch

We're also affected with a similar message, if a user is not logged into Jira.

2020-09-11 08:57:10,758 ERROR [JIM Marshaller:thread-291] [extra.jira.request.JiraChannelResponseHandler] getChannelElement Error while trying to assemble the issues returned in XML format: Error on line 4: The entity name must immediately follow the '&' in the entity reference.
-- url: /confluence/display/SPACE/PAGENAME| traceId: f74f25314edcf420 | userName: xxx | page: 470451431 | action: viewpage

Razeen Ahmad

Any resolution to this?
having exact same issue with exact same versions...

Razeen Ahmad

found a solution to this:
for us it was the 2FA app on jira causing this.
When i disabled it .. it allowed the info to pass from jira to confluence.
So for a proper fix.. i added our jira group name into the app white list feature.
Working well now.

Jan-Peter Rusch

Doesn't solve the problem on my side. I disabled our 2FA app (SecSign) on both systems (Confluence & Jira). The issue still persists.

Azraai Baharin

Yup, it is the same case for us too; JIRA's 2FA plugin. But we are struggling to whitelist our confluence based on IP (due to the nature in which we deploy it).

May I know what do you mean by "added our jira group name into the app white list feature"?

Daniel Zauner

maybe oldie but goldie:

We ended up solving this two-fold:

- on one customer setup, we used the WAN IP since it's static, so the entire AppLink traffic is taking the scenic route via WAN.

- second customer setup, we solved it at the load balancer level (routing between VMs is done on the LB machine) in combination with a custom header that's stamped only "internal" traffic

Nici Hühn

Hello everyone,
which 2FA app do you use and have you already been able to solve your issues?
For all those who use Secure Login (2FA) from syracom, I can offer to find a solution together with you.

Best regards,
Nici

Muhammad Azam_wud6v6

issue has been resolved when i set these setting

Nici Hühn

Hello everyone,

this problem is due to the fact that the Application Whitelist -> IP Filter field in the Secure Login Configuration has not been configured correctly for the respective environment.

If anyone needs support to find out the correct IP addresses of their applications, please contact us via our Service Portal. We will be happy to help you.

Best regards,
Nici

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

confluence

server

confluence-server