Looking for a way to export Jira issues AND links to Confluence pages linked to those issues

[Valerie Blondel]

Hi Community,

Quality Manager struggling here, hope that some of you will be able to help.

For audit reasons, I need to export Jira issues to Excel.  The tricky part is that I need to export the links to all linked Confluence pages as well.

As you can note from below picture, I have several Confluence pages linked to one Jira issue.

Being able to export the list would be awsome, or even being able to take a printscreen of it could work, provided I could expand it and display all Confluence pages linked to each Jira issue.

As of now, I did not find a way.

I tried to "cheat" a little bit and created a custom field (paragraph type), hoping that I could use it to store the URLs of the linked Confluence pages, preferably as short links.

(In the Paragraph custom field description I read that it is "A multiline text field hat can store longer lenghts of text.  Supports rich text like links to URLs and bold, italicized, underlined and colored text.", so I thought it would work).

I realize that this would be double work (link the Confluence page as I should in the Jira issue + copy the URL in the custom field), but if I have no other option, I would.

I cannot use a URL custom field type as I have several Confluence pages linked to each Jira issue.

I tried to create a dashboard, hoping that I could display the Confluence pages and take a print screen.  It does not work.

I tried to use the "comment" section, because it alows me to display the URL correctly, but the comment section does not seem to be exportable either.

My only option so far is to label all Confluence pages and to extract them thanks to a label macro.  This is not dynamic at all.  I have to create one label by issue, and one macro by issue too. 

• Labels are not secured, they can easily be removed if one is not paying enough attention.
• The Confluence page on which I put all the macro's become very heavy very rapidly, and I get error message because it takes too long for the macro's to retrieve the information.

Starting to feel hopeless.  Would anyone have an idea ?

Thanks so much for reading me so far !

Valérie

[Aron Gombas _Midori_ · Accepted solution]

This can be solved with the Better Excel Exporter.

It will export the links, including all types, but the default export is just showing the URL. The app enables customizing even the smallest parts of the exports, therefore you could modify the logic to make a call to Confluence and retrieve the page title if a link points to a Confluence page. The best would be to implement this is a calculated field!

A calculated field is a flexible concept and would perfectly fit this use case.

[Valerie Blondel]

Hi @Aron Gombas _Midori_  thanks for coming back to me.

As I only need to export this list a couple of times a year, I am afraid that I won't have a go, budget wise, for your solution.

Appreciate your help though, thanks a lot !

Kind regards,

Valérie

[Valerie Blondel · Accepted solution]

Hi @Marc - Devoteam 

Thanks so much for coming back to me, really appreciated.

I did what you advised and now have a wiki-style custom field.

But, upon export, here is what happens :

And what it gives in Excel :

I tried again the dashboard option, but no luck either: 

Any other trick you could think of ?  

Again, thanks so much !

[Marc - Devoteam]

Hi @Valerie Blondel 

Exporting is plain text, this will not supply the title, but just the link.

The dashboard gadget is not wiki rendered, but also juts plain text.

I even tried other marketplace apps in relation reporting using dashboard, but they show plain text the url as well.

You can look at xporter-export-issues-from-jira this marketplace is able to export in wiki markup

[Valerie Blondel]

Hi @Marc - Devoteam ,

Thanks so much for trying to help, appreciated.

Unfortunately, as I only have to export this list once or twice a year, I cant' afford the licence on a yearly base.

Again, thanks for your help !

[Marc - Devoteam · Accepted solution]

Hi @Valerie Blondel 

Please check your field configuration and the check the renderer of your paragraph field

I'm guessing it might be the renderer is not set to Wiki Style.

How-to, see modify renderer