How to export "Epic Name" field?

[Orit Nachshon]

Is there a solution for the epic name export field when exporting to excel?

[Tarun Sapra · Accepted solution]

It's an open issue tracked here.  https://jira.atlassian.com/browse/JSWSERVER-14746

Please see the comments, some people have suggested "Better excel plugin" . Otherwise you can make sure that Epic Name and Summary are same for the epic that way you won't miss the epic name field in the export.

[Tarun Sapra]

I am using JIRA 7.4.3 server version and it's working fine for me. In the CSV export of current fields I do see Epic name being exported. 

[Orit Nachshon]

DO you see it when exporting the stories? 

Of course it works fine for Epics export, but not for Stories.

[Tarun Sapra]

For stories, Epic link is exported as "Issue key" of the linked epic in my JIRA server version instead of epic name which is displayed on the stories when it's linked to epic  Is this the issue which you are talking about?

[Orit Nachshon]

Yes, this is the problem I raised.

[Tarun Sapra]

This is how it is implemented, if you want epic name to be exported instead of issue Key of the epic in the CSV export then I guess you would need to raise a ticket in JIRA

https://jira.atlassian.com/issues/?jql=

For JIRA sever project.

[Tarun Sapra]

Found an open issue - https://jira.atlassian.com/browse/JRASERVER-63305

May be you can vote , add a comment and hopefully they make the summary of the issue more descriptive. 

[Tarun Sapra]

Please upvote/accept the answer if your satisfied with the response.  Thanks!

[Paolo Franco Solinas]

Scroll down to the bottom of this thread and see my comment to visualize this in MS Excel export

[Paolo Franco Solinas]

i recently started using the Get Jira Data Excel add into import data from Jira. I have the Jira Cloud version. For having the name of the Epic on report i included the Epic Link.Name field.

Please upvote/accept the answer if you're satisfied with the response. Thanks!

[Eric Strugatsky]

Thanks!!!

[Gerta Mone]

Thanks! Very helpful! 

[Robert S]

Looks good.  Asking my IT department to download/install it (I am restricted).

[Tim Cammann]

Works great. Thanks!

[Deleted user]

I tried searching the marketplace for apps and I couldn't find a plugin by the name of " Get Jira Data" or " Get Jira Data Excel".

Can you post a link to the exact plugin/app that you're using, @Paolo Franco Solinas ?

[Barry Duncan]

Marcelo, you need to download the excel plugin for Jira outside of Jira.

https://marketplace.atlassian.com/apps/1221301/jira-cloud-for-excel-official

That's it there.

[Stefanie Lang]

Hi @Paolo Franco Solinas , how did you manage to get the Epic Link Name into the field list for the Jira Query add-in?  We only have epic name and epic link. 

Thanks so much in advance,

Steff

[Matthew.Leach]

Same as Stefanie - that field does not show up in my list (using Cloud). 

[Mike Jones]

This is what I was looking for!  Thanks!

[Yifei Wu]

Thanks!

[Mr. Gray]

This does not work. The linked issues.linkName populates incorrect information and a lot of cells are empty.

[Mateusz Przybyłek]

It is also in Cloud version. Just expand Epic link field

[Vaishali]

Thank you, Mateusz, this worked.

[Smita]

Save the result as HTML and Open it in an Excel workbook : that helps.

You can see all your Epic Names

[Josh Sommers]

That is not an option on the cloud version of JIRA.

[Apryl Harris]

Potential workaround to export Epic Name (Jira Cloud)

One could use Plans (i.e. Advanced Roadmaps) and share as CSV. This will export with the Epic Name in a column ='Parent'. Seemed to work for me.

Note: Be sure to adjust the exclusion days in the configuration if you need to. This changes the results of the plan based on the number of days after the issue is done.

[Tomasz Kustrzynski]

@Orit Nachshon You can export any field with https://marketplace.atlassian.com/plugins/com.sngtec.jira.cloud.exporter/cloud/overview. Including Epic Name.

[Orit Nachshon]

My instance is on server, not cloud... thanks!

[Deleted user]

Really?  a few hundred to a few thousand $/year just to be able to export properly?

This is ridiculous.