Need the user story extract/excel import to allow text instead of key to display same as in HTML/Jira report views. When using HTML export of user stories the epic link will show as 'text' (name is shown) instead of the epic issue key. Same applies in the Jira views and reports. This is really helpfull since the key does not give context info of the epic for the listed user stories. I was asked to automate the export for reporting purposes and found that the csv and excel plug in te get Jira data in excel, both only provide the key and mess up my report views as well relevant stakeholder info is missing now, since the epic textual description is not available anymore. So automation is also not possible to replace the manual extraction via HTML.

I understand the Jira issue but both the key and name of the epic would be very useful when extracting to /importing in excel the user story data.

I too would like to see this issue reopened and resolved. 

The explanation that this is expected behaviour is not satisfactory. I understand that the view may be that the Epic Name data belongs to the Epic itself, but if we can export another ticket type's Epic Link data it is not unreasonable to request that the name (or summary) associated with that link is also exported.

yes we need this asap

From a User perspective, I'm not concerned if it is considered a Bug or an Enhancement.  I would just like to see this deployed ASAP.  

I do a lot of Jira data analysis on Excel and the Epic Names is of course a critical piece of information for the user. 

I get around this issue with some additional Excel work as follows:

STEP 1) I need to get the list of Epic Keys separated by a comma so I can then copy/paste it to the JQL query

I use the following formula  ... =TEXTJOIN(",",TRUE,UNIQUE('Your Jira Issues'!H2:H120))

Where 'Your Jira Issues'!H2:H120 is the range of my Epic Keys from my initial Jira query

STEP 2) Create a 2nd sheet and run the following Jira JQL query on the Jira for Excel Window:   key in (list of epics separated by comma from previous step)

The Jira results with the Epic information will be displayed in a table format in 2nd Sheet.

STEP 3) Now you can use the Index/Match or VLookup in your 1st sheet to populate the Epic Name information from your 2nd sheet.

If you are familiar with Excel ... the above should take you a few minutes. Otherwise, you will need a few extra minutes to watch some Youtube videos to learn the excel functions.  

Good luck!

For reporting purposes this is a BIG improvement. Execs just see a list of issues but have no idea to what the issues relate to. Seeing a simple epic-name is very helpful.

We need this also, as soon as possible.

yes we need this asap

Agreed - this is a major issue for tracking the backlog and should be fixed. 

Please implement the requested change. There is a lot of value in being able to see the name of the epic when reviewing reports. The epic issue key adds zero value as it isn't useful for reporting.

This issue is reopened as an enhancement request.  Please add your comments and votes.

https://jira.atlassian.com/browse/JRACLOUD-78582