Activity Stream Incorrect Links to JIRA Issues

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:


Whereas I would expect it to look like this:


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.

3 answers

Same problem here.. any updates?

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

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.

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?

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.

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? 

@Stephen Gurnick: Do you know if in your environment it was needed to add the script mentioned here or if the problem got naturally fixed with the software version?

@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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Dec 18, 2018 in Confluence Cloud

Happy holidays from our team to yours!

Hi Community!  2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...

490 views 3 18
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you