How do other Confluence connect apps get summary and status for Jira issue macros?

Hey there!

Our app uses the export_view to get the content of Confluence pages. In export_view and its siblings, you only get the issue key for Jira issues. This is a shame as we’d love to show our users issues with summary and status like they are used to in the normal Confluence view.

But as everything I’ve read says this is not possible, we’ve lived with just showing the issue key. Until a customer opened a support ticket and pointed out that other apps (like the PDF exporter from k15t) include issue details in their export - without (!) installing a separate Jira app or using 3LO. I’ve checked and it’s true. So, the question is:

How can a Confluence Cloud Connect app get the summary and status of Jira issues in the Confluence content? It’s proven that it is possible by k15ts PDF exporter.

I feel like I’m missing something obvious. Would be great if somebody has a hint. Thank you!

1 Like

Haven’t tried it myself, but does the https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-body/#api-group-content-body endpoint converts the macro content? I can see a macroRenderedOutput parameter in the expand list, for instance.

Hey Corentin, thanks for the idea!

But unfortunately not. These endpoints only return a placeholder HTML tag with some attributes. It seems that the new Atlassian Smart Links implementation then picks these up and renders something on client side.

I just learned that this does not only apply to single issue links. Jira issue tables are affected as well. Not long ago, they were exported fine, now they are only a link as well. This kills a lot of established use cases for our app.

I’ve found some related CONFCLOUD issues, but there’s not a lot of traction: