Activity Stream Incorrect Links to JIRA Issues

[Stephen Gurnick]

In Confluence users have the Activity Stream gadget configured on pages to see what work has been done in our JIRA instance for a given time range.

The gadget provides links to the JIRA issues where the user updated the comments, added attachments, etc.

When I click on these links, the URL contains the name of the Confluence server rather than the JIRA server. Therefore when I click on the link I get a page not found error.

For example, a link to a JIRA issue in the Activity Stream looks like this:

https://<CONFLUENCE-FQDN>/browse/<JIRA-ISSUE-KEY>

Whereas I would expect it to look like this:

https://<JIRA-FQDN>/browse/<JIRA-ISSUE-KEY>

On other Confluence pages we are using the JIRA Macros add-on to link directory to issues and those links work as expected.

The problem only seems to be with the Activity Stream linking to JIRA issues.

I am running Confluence 5.5.7 and not sure of how to troubleshoot this.

Thank you for your help.

[Stephen Gurnick]

This might have been an issue with the version of Confluence I was running at the time (version 5.5.7)

I have since updated to Confluence 5.7.4 and I no longer see this issue.

[Alberto De Luca]

I'm on Confluence 5.7.4  as well, but the issue seems to be still present for me when linking to Jira projects - what Jira version are you using?

[Stephen Gurnick]

We are now at JIRA 7.6.6 and Confluence 6.6.3. I haven't see this issue since my update to Confluence 5.5.7 back in 2016.

[Alberto De Luca]

Our environment is currently running JIRA v6.4.13 and and Confluence 5.7.4:
links to JIRA issues opened from the Activity Stream in Confluence have the wrong url (pointing to the Confluence server rather than to the JIRA server) - is there any known workaround or tweak to get this fixed? I'm brought to think it may be related to Confluence settings only - anyone who can provide some more insights? 

[Alberto De Luca]

@Stephen Gurnick: Do you know if in your environment it was needed to add the script mentioned here https://jira.atlassian.com/browse/JRASERVER-41293?focusedCommentId=1841629&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1841629 or if the problem got naturally fixed with the software version?

[Stephen Gurnick]

@Alberto De Luca: After our update from version 5.5.7 to 5.7.4, this issue went away. I did not have to add any scripts or perform additional actions.

[tcerami]

I am experiencing the same issue.  Any updates on this?

[thekngmkr2015]

Same problem here.. any updates?