How to export the parent key instead of parent ID?
Asked by Guusje Evers:

Hi all,

We have recently added the AIO tests to our jira environment. In order to bulk import jira tickets, I have to make regular exports - after every sprint, the stories need to be exported to excel and then imported into AIO tests.

I would like to export the parent issue key into the excel, such that we can easily find the corresponding epic in the testcase. However, when I export the standard jira field "parent" I will get the parent ID, not the key.

Is there any way to export the Parent Key in the standard XXX-123 format?

Thanks in advance!


Answers:
author: Noopur Varshney _AIO Tests_
body: Hi [@Guusje Evers](/t5/user/viewprofilepage/user-id/5452858)

If you use parent or epic link as shown in the screenshot below and then export in excel using the highlighted option, you should get the key as shown in the second screenshot. I have sent response on our ticket too. Hope you have received it.

![search 1.png](https://community.atlassian.com/t5/image/serverpage/image-id/329500i3AB156DDB53B0772/image-size/large?v=v2&px=999 "search 1.png")![result -1.png](https://community.atlassian.com/t5/image/serverpage/image-id/329501iC2B373EA50EED2C5/image-size/large?v=v2&px=999 "result -1.png")

Once you link the cases with the Jira stories, you don't need to export Jira tickets after every sprint.

The Jira tickets can directly be accessed from the test case in AIO Tests and vice-versa, the cases can be accessed from the Jira ticket too.

Hope this helps!

Cheers

Noopur (AIO Team)

comments: author: Guusje Evers
body: Hi Noopur,

Unfortunately it doesnt work like that in our environment.. When making the right selection in the Jira export, there are 3 possible colums:

1. Parent: this column retrieves all parents from our stories. However, if we export to excel, the column gives back the parent ID in the format 12345 instead of KEY-ABC. See column J in photo below

2. Epic link: this column retrieves parent issues of 1 parent issue type (green circled screenshot) not the other one (orange circled). With export it gives KEY-123 tho, which is good. See column L in screenshot below. No link is exported..

3. Parent link: this column retrieves the orange circled parent issues, not the green circled ones. See column N, also no link exported.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/329908i18300ADDC67F04BE/image-size/large?v=v2&px=999 "image.png")  

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/329907iBF01B70C573FFDF1/image-size/large?v=v2&px=999 "image.png")


author: Guusje Evers
body: ah nevermind, I always exported using CSV Excel - but just found the Excel for Jira app! Links were exported! Also the Parent colums are links now :) Thanks!


author: Bouke Krediet
body: Hi all! I have exactly this issue, but then the other way around.

I want to see Parent ID's in the jira export, but am only seeing parent keys/links

Any idea how i can get Jira to export these values? I need them for proper hierarchy in a new jira environment. Working on a DC to DC migration.

Kind regards,

<br />

Bouke

comments: author: Aron Gombas _Midori_
body: [@Bouke Krediet](/t5/user/viewprofilepage/user-id/4121585) You can customize the [Better Excel Exporter](https://marketplace.atlassian.com/apps/1212652/better-excel-exporter-for-jira-xlsx?hosting=cloud&tab=overview) to export the parent ID! With or without the corresponding hyperlink.

You only need to make a simple change to "field-helper-tool.groovy" for this.

If you can't find how to do this, [ask our support](https://www.midori-global.com/support/customer-support) any time and they will guide you!

*(It's a paid and supported app developed by our team.)*


author: Guusje Evers
body: If you use the export CSV function, you'll get the parent iD's - not the keys. At least that's what was in my case.


author: Aron Gombas _Midori_
body: Our [Better Excel Exporter](https://marketplace.atlassian.com/apps/1212652/better-excel-exporter-for-jira?hosting=cloud&tab=overview) app supports this!

There is a [calculated field](https://www.midori-global.com/products/better-excel-exporter-for-jira/cloud/documentation/calculated-fields) named "Excel parent key" which does *exactly* what you want:
> Key of the parent issue or a blank string if the current issue is not a sub-task.

There is even a boolean setting "issueKeyAsLink" to make the exported key a link to the parent issue or not.

It takes a few clicks to configure it. Give it a try!

*(It is a paid and supported app developed by our team. Free for 10 users!)*


Tags: aio

cloud

jira-cloud