Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

With the change from Epic Link to Parent how do I get the Epic name or summary of the parent issue

Ron McFarlane February 7, 2024

Up until when Epic Links were replaced with the parent field, I could write some JQL that would extract the columns I wanted. I would then use the Jira/Excel addon to export the results directly into Excel. Once in Excel from the Import Data from Jira addon panel you can go to the Fields tab, click on edit, search the fields by Epic and then scroll down to Epic Link and there is a dropdown that will allow you to select Epic Name.

This would then include the name of the Epic in the extract of the issues.

Now when I  add an issue to an Epic and run the same extract the EPIC Name field is empty. Older issues still have the Epic Name.

 

I am assuming now the epic name is no longer being populated.

 

That's  the long story and my request is how do I get the Parent Summary value of an issue to be to be included using JQL.

 

Thanks

 

 

 

3 answers

0 votes
Hannes Obweger - JXL for Jira
Atlassian Partner
April 4, 2025

Hi @Ron McFarlane,

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the parent summary.

This is how it looks in action:

parent-summary-export.gif

As you can see above, you can easily sort and filter by the parent summary, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Plus, it is of course included in any XLSX or CSV export of your sheet.

Any questions just let me know,

Best,

Hannes

0 votes
Aron Gombas _Midori_
Community Champion
February 8, 2024

If you export the "Parent" field with the Better Excel Exporter, we export the key, the summary and even the issue type of the parent. The first two are required in almost every case, and the third one helps to identify if it is a issue-subtask type of relation or an epic-story one, for example.

Actually the format of the value can be freely customized if it is too much or too little information!

image.png

Catherine_Moody August 7, 2024

For those of us that don't have Better Excel Exporter, any way we can get this functionality back? We use Get Jira Data in my organization. The Parent ID isn't as helpful as the "summary/name" of the Parent ID.

Also note: If I use the the export Excel from Jira it is missing the summary, if I Export HTML from Jira it is missing the Summary ID, I use this field to create hyperlinks. Ultimately, how do I get information using Get Jira Data API in Excel.

 

0 votes
John Funk
Community Champion
February 7, 2024

Hi Ron,

Not sure that I exactly follow your scenario, but you would just use the parent field and the issue type. If the issue is an Epic, then the Summary field is the "Epic Name". If it's not an Epic, then the Parent field will have the value of the Epic key. 

Bobby Moyini
Contributor
November 12, 2024

The problem is when you use the jira plugin the parent field lists the key only and no name. What the other user wants is the plug-in to display the parent name. The epic name field is not tied to the issues like the parent key is. 

 

I have this exact same issue which makes the plugin less useful for me. I end up exporting my filter manually , which exports epic link name or parent summary. Both have the names of the epics that are tied to the issues that are linked.

 

I wish the jira xls plug in could export the parent summary. 

 

 

Like Ilya Maximenko likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events