nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why doesn't 'Epic Name' show any results when querying?

Jennifer_Molyneaux

Hey Everyone -

I'm trying to figure out why the column for 'Epic Name' is empty when I query stories in JQL. We're not using Next-Gen projects - so I've ruled that issue out. Anyone know how I can get this column to show the Epic Name? When I export my results, I want the name of the Epic to show in the csv. If I export the Epic Link, it just gives me a ticket number so I have to do a separate query to actually get the name for each of those linked Epics.

Accepted answers

Jack Nolddor [Sweet Bananas]

On Stories, you should use Epic Link field .

Epic Name is only populated on Epics elements and used as a label on the Epic Link dropdown on Stories. So there is no way to retrieve such information on CSV at Story level.

Regards

Bill Sheboy

Hi @Jennifer_Molyneaux

You are correct that this cannot be done with standard Jira JQL queries.

I run into this same situation when exporting information to provide more advanced reporting than is available in out-of-the-box Jira. Here is what I do:

Export my child project data (stories, bugs, tasks), including the epic link field
Separately, export all of the epics, including the epic name field
Bring both of these CSV files into one spreadsheet
Add a formula to lookup the Epic Name from the epic data to associate to the children's Epic Link field: child's Epic Link = epic's Key

Best regards,

Bill

Ste Wright

Hi @Jennifer_Molyneaux

I have an alternative using Automation for Jira - I expect it'll also be possible using a script add-on such as ScriptRunner

Automation for Jira allows you to automate actions - such as updating a field - based on a trigger event - such as an issue being created or updated.

This is how I did it using Automation:

Create a new single-line custom text field - eg. "Parent Name"
Don't add the field to a screen - it can still be populated even if not on a screen
In Automation for Jira, create a new rule
Add a Trigger - for example, issue updated (this would cover the Epic Link)
Add an Action - to update the field "Parent Name", copying the value from the child issue's Epic parent, specifically the Epic Name field
Create the rule, give it a name and activate it
Go to an issue and update it - eg. remove / re-add the Epic Link
Next, go to your issue search page and add "Parent Name" to your list of columns. This will have populated with the Epic's name
Export the data

As the text field has copied the text from the Epic Name, it'll be text rather than the Epic's issue key. This saves the manual steps in excel to join the text together.

The solution suggested by @Bill Sheboy is a good alternative though - if you don't have these apps or are unable to get them, this is what I would suggest also

Ste

All comments

Jack Nolddor [Sweet Bananas]

On Stories, you should use Epic Link field .

Epic Name is only populated on Epics elements and used as a label on the Epic Link dropdown on Stories. So there is no way to retrieve such information on CSV at Story level.

Regards

Jennifer_Molyneaux

Epic link won't get me what I need but I appreciate the clarification, that's helpful.

Jack Nolddor [Sweet Bananas]

Thanks for you kind words.

Did my initial answer solve your doubts?

If so, consider to mark the proposed solution as an 'Accepted answer'. This will help other people with the same or a quite similar problem to find a solution in a easy and faster way.

In addition, by doing this the post will automatically gain the "Solved:" prefix in search results to indicate other people that no further support is needed.

Kind Regards.

Bill Sheboy

Hi @Jennifer_Molyneaux

You are correct that this cannot be done with standard Jira JQL queries.

I run into this same situation when exporting information to provide more advanced reporting than is available in out-of-the-box Jira. Here is what I do:

Export my child project data (stories, bugs, tasks), including the epic link field
Separately, export all of the epics, including the epic name field
Bring both of these CSV files into one spreadsheet
Add a formula to lookup the Epic Name from the epic data to associate to the children's Epic Link field: child's Epic Link = epic's Key

Best regards,

Bill

Jennifer_Molyneaux

Hey Bill -

This is just what I was looking for in terms of a workaround. Thank you so much!!

Ste Wright

Hi @Jennifer_Molyneaux

I have an alternative using Automation for Jira - I expect it'll also be possible using a script add-on such as ScriptRunner

Automation for Jira allows you to automate actions - such as updating a field - based on a trigger event - such as an issue being created or updated.

This is how I did it using Automation:

Create a new single-line custom text field - eg. "Parent Name"
Don't add the field to a screen - it can still be populated even if not on a screen
In Automation for Jira, create a new rule
Add a Trigger - for example, issue updated (this would cover the Epic Link)
Add an Action - to update the field "Parent Name", copying the value from the child issue's Epic parent, specifically the Epic Name field
Create the rule, give it a name and activate it
Go to an issue and update it - eg. remove / re-add the Epic Link
Next, go to your issue search page and add "Parent Name" to your list of columns. This will have populated with the Epic's name
Export the data

As the text field has copied the text from the Epic Name, it'll be text rather than the Epic's issue key. This saves the manual steps in excel to join the text together.

The solution suggested by @Bill Sheboy is a good alternative though - if you don't have these apps or are unable to get them, this is what I would suggest also

Ste

Jennifer_Molyneaux

@Ste Wright - this is perfect!! Thank you so much!!

Madlen Göhring

Hi everyone,

I just added @Ste Wright suggestion to our Jira instance and this is the updated instruction for the new issue view.

Create a new single-line custom text field - eg. "Teil von"
Add the field (at least) to the view screens of the Issuetypes you will run the jql on
In Automation for Jira, create a new rule (copy from the picture)
Create the rule, give it a name and activate it
Go to an issue and update it - eg. remove / re-add the Epic Link
Next, go to your issue search page and add "Teil von" to your list of columns. This will have populated with the Epic's name
Export the data

Automation Partof.PNG

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server