nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to export to excel with parent column?

Marcus Widerber

Hello,

I want to export issues to excel.

I am using subtasks.

I want to order the subtasks by their parent, report on them by parent task, etc. (in excel)

Therefore, it would be good to get the parent key in the export.

AFAICS, there is no parent key column or similar that can be exported.

Surely, this must be possible?

How else is one to use the excel export to view and report on parent-subtasks?

Any help appreciated.

Accepted answers

Nic Brough -Adaptavist-

I've used simple derived custom fields to do this in the past (requires a bit of code - I've always done it with a really basic plugin, but I think it can be done with the script-runner addon as well)

All comments

Nic Brough -Adaptavist-

Marcus Widerber

Yeah, it seems that workarounds are needed again. Thanks Nic.

Marcus Widerber

Including a parent reference in the dataset has been rejected by atlassian, this is the "new feature" that was rejected:

https://jira.atlassian.com/browse/JRA-21555

Lets hope that they reconsider. Most packages process data with parent references in a more direct and natural way.

Contact Kintosoft

Links Hierarchy exports issues into Excel by preserving the hierarchy in a very flexible way as you can visualize the hierarchy in JIRA previously, apply filters, expand/collapse children, etc and once you view the right data then just click on the "Export to Excel" menu and Links Hierarchy will create a powerful report with support for expand/collapse (from Excel!!!), configure issue fields to export, etc.

KRC

Hi Nic. Can you please elaborate your procedure to solve the parent subtask reporting?

Nic Brough -Adaptavist-

Not much - I use a scripted field (ScriptRunner) which reads the current issue and echoes out the parent issue summary and/or key on all sub-tasks, and the parent (slightly annoying as it's duplicated data on the parent, but it lets you sort and export the data easily, so hey)