Forums

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

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

Jennifer_Molyneaux April 9, 2020

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. 

4 answers

3 accepted

0 votes
Answer accepted
Ste Wright
Community Champion
April 10, 2020

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:

  1. Create a new single-line custom text field - eg. "Parent Name"
  2. Don't add the field to a screen - it can still be populated even if not on a screen
  3. In Automation for Jira, create a new rule
  4. Add a Trigger - for example, issue updated (this would cover the Epic Link)
  5. Add an Action - to update the field "Parent Name", copying the value from the child issue's Epic parent, specifically the Epic Name field
  6. Create the rule, give it a name and activate it
  7. Go to an issue and update it - eg. remove / re-add the Epic Link
  8. 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
  9. 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 April 14, 2020

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

Like Ste Wright likes this
0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 9, 2020

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 April 9, 2020

Hey Bill - 

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

Like # people like this
0 votes
Answer accepted
Jack Nolddor _Sweet Bananas_
Atlassian Partner
April 9, 2020

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 April 9, 2020

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

Jack Nolddor _Sweet Bananas_
Atlassian Partner
April 9, 2020

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.

0 votes
Madlen Göhring
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 15, 2021

Hi everyone,

 

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

  1. Create a new single-line custom text field - eg. "Teil von"
  2. Add the field (at least) to the view screens of the Issuetypes you will run the jql on
  3. In Automation for Jira, create a new rule (copy from the picture)
  4. Create the rule, give it a name and activate it
  5. Go to an issue and update it - eg. remove / re-add the Epic Link
  6. 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
  7. Export the data

Automation Partof.PNG

Suggest an answer

Log in or Sign up to answer