Previously, Epic Link field for issues would contain the value of the Issue Key. After the change: Upcoming changes: 'epic-link' replaced with 'parent', exporting the same data is not possible because the Epic Link field is no longer used. The user likely sees the message: "Epic Link will soon be replaced with Parent. Use the Parent field instead"

The current CSV export feature includes the parent issue ID, which is primarily used for internal system purposes and offers limited value to users.

This feature request proposes adding an option to select the parent issue key to be included in the CSV export. The issue key is more meaningful and recognizable for users, allowing them to easily reference and understand the parent-child relationships between tickets.

This change will enhance the usability of exported data by providing relevant and accessible information for analysis and reporting.

Workarounds

1. With a bit of scripting, it is possible to automate adding the Parent Issue Key to CSVs by using the parent ID as a reference to extract the issue key from the response JSON, using the endpoint Jira REST API - Get issues
2. Use the Open in Microsoft Excel or Open in Google Sheets options - though not all fields are supported in these methods, most fields are supported and both options will export the parent key with a link to the issue
3. Marketplace apps - the apps offer a free 30-day trial, so it is possible to test them to see if they meet your needs
4. 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.