parent issue key is missing when exporting Jira Plans to CSV

Question

when exporting an Jira Plans plan into CSV there is column "parent" which delivers the title of the parent issue (e.g. of the parent initiative of an epic etc.).

but without the parent key it is sometimes impossible to recreate the hierarchy based on the export since the parent issue key is missing and sometimes parent and child might have the same title.

to me this looks like a bug and could be fixed easily by either adding the parent issue key to the export or allowing more configuration possibilities to the user when exporting.

Nimanpreet Kaur · Answer

One of the workarounds that we may use is as follows:

Create a new field to hold the parent key and an automation rule to fill that field. Depending on how often you need to export the results, you can set it to trigger whenever the parent is updated, schedule the rule to run, or manually trigger it before you export the issues. It might also be necessary to create a rule to update the existing issues that have parents. Once the field is filled, it is possible to simply add this field to the CSV export.

I hope this helps with your given use case.

jeroen.wilmes · Answer

when I export a plan in Jira to a csv file and i have choosen the field "parent". The export only has the summary of the parent and misses the issue key from the parent, where both are displayed in the field "parent" on my plan.

The field "parent" in plan looks like a merge of issue key of the parent and the summary. If not both, I would prefer the issue key to be exported. (from the issue key I can search for more information, but that is much more complicated with the summary.
I'm only working with company managed projects.

Ludwig Bayerl · Answer

Thanks @Hannes Obweger - JXL for Jira , I get what you're saying.

But Jira Plans offers a CSV export which I cannot simply recreate by other means - at least I am not aware. An API access for Jira Plans is as well only in consideration phase currently (https://jira.atlassian.com/browse/JSWCLOUD-20360)

My concern is that then you offer an export which delivers "issue key" and "issue title" and "parent" then I'd expect the "parent key" to be there (with "parent title" as a bonus) and not just the "parent title" which can be ambigous.

This looks like a standard requirement to me whenever you offer an export which contains a relationship to another object which is only uniquely identifyable by it's key/id.