How to force include macro to render Jira links?
Asked by bobby.langhorne@ormutual.com:

I have a page in Confluence with multiple links to Jira stories. I am using the Jira macro to render the Jira links so that the story number and name are included automatically in the link. This is working fine. However, I have a page where I am using the include macro to include the first page. On the page with the include macro, the Jira links do not always render correctly and are merely links to Jira (i.e. http://\<OurJiraUrl\>/browse/\<Jira Story Number\>).

How can I force the Jira links in the include macro to render correctly every time?


Answers:
author: Shannon S
body: Hi Bobby,

Thanks for raising this with us.

If I understand you correctly, you're using the [Jira Issues macro](https://support.atlassian.com/confluence-cloud/docs/insert-the-jira-issues-macro/) to display multiple Jira issues in a page in Confluence. This allows your users to click the issue link and get the full URL in Jira, including the specific issue number. However, when you display this same information using the [Include Page macro](https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/), the URL is only directly to the Jira site, and not to the issue itself.

Do I have that right?

Could you show me how you have the Jira issues macro set up? Are you inserting as a JQL query, or individual issue numbers? I'd also like to see any examples of the behavior, if you have a screenshot you would be able to share. Feel free to censor out sensitive information.

Thanks, Bobby!

Take care,

Shannon

comments: author: bobby.langhorne@ormutual.com
body: It seems to have lost my previous reply, so I will try again.

Shannon, your summary is correct. We are using the Jira Issues Macro, by selecting individual issue numbers.

Here is the primary page, with the Jira Issues Macro being used:

![GoodLinks.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/107562i99B76944F21A6E92/image-dimensions/625x162?v=v2 "GoodLinks.PNG")

When we reference the above page in a second page, using the Insert Page macro, the links do not render with the above formatting. Instead, they look like this:

![BadLinks.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/107565i8879E6F12F0363BD/image-dimensions/329x161?v=v2 "BadLinks.PNG")

Both Confluence pages are in the same space. The first page is a child of the second page. We would like the second page, with the Insert Page macro, to render the Jira links in the same way as the page it is inserting.

Thank you,

Bobby


author: Shannon S
body: Hi Bobby,

Thank you for confirming that with me, and for providing the screenshots as examples.

The issue you've encountered is related to the following bug:

* [CONFCLOUD-67960](https://jira.atlassian.com/browse/CONFCLOUD-67960) *Include Page macro breaks the layout of the source page's contents*

I already tested it with the workaround mentioned, but it doesn't have any effect in this case.

What's happening is that you created the list of Jira issues on a page using the New editor. The new editor appears to be display single issues as a Smart Card link instead of a simple Jira issues macro. So, when you use the Include Page macro, because of the bug, it's attempting to display the content using the Legacy editor technology, which strips the formatting.

The only method that works for me currently is to use the Legacy editor to create both pages. I personally don't think the format looks as nice as it does on the New Editor page, but it's a workaround for the time being.

I'm trying to see if we can get an update on that bug ticket, so please go ahead and subscribe to it, so you can see when there is progress.

I hope that's clear, but can you let me know if you have any questions about that?

Thank you,

Shannon


author: bobby.langhorne@ormutual.com
body: Thank you


author: Shannon S
body: You're welcome, Bobby!

I've been in touch with the development team, and it's something we'll be able to address in our short term backlog.

Thanks again, and take care.

Shannon


Tags: cloud