exactly - thank you sometimes it's hard to find the correct issue

Hi oliver.straesser, it sounds like you're running into CONF-36648. You can add yourself as a watcher on that ticket and you'll be notified of any updates.

Hi

we installed the JIRA Macro 5.6.11 Add-on and have different App Links as Display URLS configured.

But the Icons of the JIRA Issues aren't loaded, because the app link is used to link the image url.

Should I open a new case, or did I missed a configuration.

Cheers
Oli

Thanks for pointing this out Jeff! I've actually spoken with the Application Links people and I have some more information.

In Confluence 5.3 and JIRA 6.1 (Applinks 4.0) the Application URL will be automatically set to the Base URL of the instance. You will still be able to update the Display URL of the link.

As we know from tickets like this one, that is not always a viable configuration, and customers often need to create the link with a URL that is not the Base URL, to bypass proxies, SSL etc.

The current workaround in that case is to set the BaseURL of the applications to the URL you want to create the link with, then create the link. The Application URL for both applications will be their BaseURL. You can then set the BaseURL back to the correct user-facing URL, and edit the Display URL of the application link.

This issue is being tracked here for Confluence: CONF-32611

That's done it, thanks for the clarification!

Hi Tristan,

The fix for this wasn't landed on time by the time we released 5.3.1 bug fix version for Confluence 5.4.1. You can now download and install 5.3.2 which has the fix. Sorry for the late response.

Nguyen

Can anyone shed any light on why this still wouldn't be working on Confluence 5.4.1 with JIRA Macros 5.3.1?

We're using JIRA 5.2.9, does that need to be upgraded to some particular version in order for the fixed JIRA Macros to work? Seems irrelevant, since I can get a table of issues to render, they just have incorrect links.

We upgraded to Confluence 5.4.1 and JIRA issues are still linking to the application URL instead of the display URL. Clicking the link then sends the user to http://localhost:8081/browse/... which doesn't work.

I checked the JIRA Macros add-on version and it is 5.3.1. Do we have to do something different in order for the link to use the display URL instead of the application URL? Or maybe the fix is missing from JIRA Macros 5.3.1?

The only thing I got to work was selecting multiple issues and choosing "Total issue count" under display options. This links correctly using the display URL. Single issue or Table formats are not working.

For us too. But got another one. The Team Calendar ist still using the Application Url instead of the DisplayUrl.

The add-on is now working correctly for us. Thank you to everyone involved for the fix.

The fix for incorrect icon link is now included in 5.2.2 release : https://marketplace.atlassian.com/plugins/confluence.extra.jira/versions#b4176

david.zahorsky, chris.milam Thank you for your report. Let's leave this reopened until the problem with image URL is resolved.

I am seeing the same behavior as David Zahorsky. The link now correctly links back to JIRA, however the Issue Type and Issue Status icons still use the Application URL instead of the Display URL. The result is that the page attempts to load the images for several seconds (of course it can't, because it is trying to access them with the Application URL...same issue as before), and eventually white boxes are displayed instead of the proper images.

Please re-open this issue, as it is not yet resolved.

– Note: To demonstrate the issue, right click on the white box (where the image should be) and select "Copy Image URL". When you paste this text elsewhere, you should see a URL containing the Application URL instead of the Display URL.

Thanks Nguyen... The link itself works now. But the little Icon's still hold the old url. (Issue Type and Status Icons)

New version of Confluence JIRA plugin has been released on Marketplace, please check it out https://marketplace.atlassian.com/plugins/confluence.extra.jira

Ok – thanks for the confirmation, Dang.

Will you post back here when that is released?

mlb Sure.

We're running Confluence 5.1.5 with the 5.0 version of the JIRA Issues plugin. Will the 5.2.1 release of the plugin support versions of Confluence older than 5.3?

tolive I am so sorry, the 5.2.1 release only supports Confluence 5.3+

We're running Confluence 5.1.5 with the 5.0 version of the JIRA Issues plugin. Will the 5.2.1 release of the plugin support versions of Confluence older than 5.3?

We are also releasing JIRA Issues Macro 5.2.1 bug fix version, will be available on Market place in the next couple days.

Will you post back here when that is released?

chris.milam development-team This fix will be bundled on Confluence 5.4.1 release. We are also releasing JIRA Issues Macro 5.2.1 bug fix version, will be available on Market place in the next couple days.

I also have the same question as Chris Milam.

This has been changed to resolved, but when will the bug fix be released? Will this be fixed with JIRA Issues Macro 5.3? (5.2 was just released.)
This linking issue is impeding our use of JIRA and Confluence, so please release ASAP!

I see that the status has been changed to Resolved. Will this bug be fixed with JIRA Issues Macro 5.3? If so, is there a target release date?

It scares me how easy it is to cause a bug like this. As a workaround for current case we used our external url for display and application url. For optimization we pointed that external url to internal ip in hosts file. This gives internal network speed without the danger of having similar bug in any of the add-ons.

Thanks a lot, Atlassian!

Go Nguyen Dang! You can do it. Code hard!

LIKE!

you'll make my day, if it will be fixed for CF 4.3.7 as well

You made my day

thumbs up for the in progress state!!

Fo shizzle!!!

Yo man dis be straight up BUSTED. How is I supposed to be impressing all da hotties wit my mad dev skills when my workflow is straight up jacked? Why you can't get yo links straight? Lil hustlas in tha hood write better code in notepad, namsayin? It ain't like I'm askin ya'll to integrate pizza ordering or nuffin, I just want my damn LINK to work. That be what links do, yo. We ain't talkin about chicken and gravy.

Ya'll best fix my confluence with a quickness.

I'm really impressed on the ignorance of this major issue by Atlassian.
Never seen something like this in the whole Atlassian history:

• This is a big pain especially for enterprise customers...
• This is affecting the combination of both major Atlassian products to work together
• Customers have to live with this for over half a year now

Atlassian: For what are we paying SW-Maintenance?
This is/was core functionality of your two main products and it stopped working!
To say it in your words: Don't fuck the customer...

Since the update the team calendar has the right links. But the Jira Macro bug still persists.

+1 again.

An update to the JIRA Macros addon (from 5.1.3 to v 5.2) was released on 08 Nov 2013.
I updated the JIRA Macros addon to 5.2 within Confluence, and this issue persists and the update did NOT resolve it.

ATLASSIAN PLEASE ADDRESS THIS QUICKLY.
Linking Confluence with JIRA issues is BROKEN.

Same bug here...

Mucks up linking to JIRA issues from Confluence, which would otherwise be a very useful organizational tool. (*The reverse links are messed up, too…)

As of 11/11/2013, this issue is NOT resolved. I have just updated my company's JIRA/Confluence instance to the latest releases (JIRA 6.1 and Confulence 5.3), and now our application linking is broken.

This is a blocker for us, as our application deployments depend on being able to reference JIRA issues from within Confluence.

Atlassian, please address this issue quickly.

+1 - I got the same bug on my environment.

+1 and BUMP!

Linking to JIRA Issues from Confluence is NOT working! I opened a support ticket, and the support rep was able to duplicate the issue. He directed me to this issue (CONF-29182) as a confirmed bug, and he added Confluence 5.3 to the list of affected versions.

I'm using the following and have confirmed that anytime I insert a link to a JIRA issue via the JIRA Macros v 5.1.3, the link that is rendered uses the application URL instead of the display URL:
JIRA v 6.0.7, Confluence v 5.3 with JIRA Macros v 5.1.3.

I also asked for a solution on the answers forum, but was directed to this issue also.
(https://answers.atlassian.com/questions/227450/confluence-shows-application-url-instead-of-display-url-when-inserting-a-jira-issue-via-jira-macros-addon)

This is a major issue, as we cannot link Confluence collaboration correctly to JIRA issues, and makes using JIRA with Confluence a little pointless. Having team collaboration integrated with project/issue tracking was the sole reason we are attracted to these Atlassian products.

We really need this issue resolved so we can use it internally and also roll this solution out to our clients.

We would like to have this resolved as well because this severly affects Windows Authentication SSO environments for Jira + Confluence

This is a major issue in making our JIRA SSO: Having SSO (custom SSO authenticator) implemented in JIRA, we need to configure the application link using normal authentication and therefore another url/port to access JIRA by Confluence.
But it finally results in false links using the jiraissues macro on a confluence page.
Thanks for resolving this quickly!
Cheers, Philipp

Thanks for clarifying that Jeff, I'm going to reopen this ticket. Sorry for the misunderstanding!

-Denise.

Denise,

I don't think this is fixed. I can still replicate this bug in Confluence 5.1.3 with v4.0.29 of the JIRA Macros plugin. CONF-22283 is related (I'm the one who linked it) but not the same.

Specifically, if I add a jiraissues macro with the URL being the 'application' URL (http://jira.localhost/sr/...), then the wrong URL is present in the search link (above the search results, by default titled "JIRA Issues"). The displayed issues' links have the correct URLs.

This was resolved in https://jira.atlassian.com/browse/CONF-22283