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.
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:
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Bill -
This is just what I was looking for in terms of a workaround. Thank you so much!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Epic link won't get me what I need but I appreciate the clarification, that's helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone,
I just added @Ste Wright suggestion to our Jira instance and this is the updated instruction for the new issue view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.