How to export subtasks mapping in CSV

[Diego MEDICS]

Hello, 

i want to export all the tickets in the project but also mantaining the link with the child issues. 

is this possibile with the native capabilities of jira?

[Pasam Venkateshwarrao]

Hi @Diego MEDICS 

Welcome to the community,

Standard JQL doesn't easily allow it, but you can quickly find the results using our professional indexing service JQL Search Extensions

You can use this function to help you in your request:

ChildrenOfIssuesInQuery

For a given JQL subquery it finds children of resulting issues. It supports Advanced Roadmaps “Parent Link” and a standard Jira hierarchy Epic → Story → Subtask. Also have a look at ChildrenOfIssuesInQueryRecursive.

Examples:

issue in childrenOfIssuesInQuery("project='ABC' and type=Epic")

Finds all epics in project ABC.

[Jack Brickey]

@Pasam Venkateshwarrao , what about the native method is missing here? Maybe there is something more in @Diego MEDICS a requirements that would lead us to a non-native solution and hopefully he will chime back in here soon. However I am always in learning mode and I my usage/needs for export are narrow so please share your experience here.

[Pasam Venkateshwarrao]

@Jack Brickey I have tried with JQL extension app with the queries it showed me as child issues of particular issuetype of a project.

[Jack Brickey]

By JQL extension app are you referring to the Official Excel/Sheets extension or something else?

I was simply using the export function built into Jira not the aforementioned extension (although I would expect similar results with the excel/sheets extension, and will have to test) and was able to obtain the results as seen in my reply to John here. Basically, you should get the parent and issue IDs which provides hierarchical mapping. The obvious downside is that it isn't in hierarchical order but that can be obtained with a bit of spreadsheet magic.

[John Funk]

Hi Diego - Welcome to the Atlassian Community!

You should export the Sub-tasks (not the parents) and include the Parent field in the filter before exporting. 

To get all of them in one shot, you would need ScriptRunner or something similar. 

[Jack Brickey]

@John Funk ,

I am not following. I just did a quick test export and got this.

Issue key	Parent	Issue id	Issue Type	Summary	Status	Priority	Parent summary
TWM-34	10640	10641	Sub-task	sub of TWM-33	To Do	Medium	another task in TWM
TWM-33		10640	Task	another task in TWM	Open	Medium
TWM-32	10572	10639	Sub-task	another sub o TWM-30	To Do	Medium	Approval testing w/ automation routing #1
TWM-31	10572	10638	Sub-task	sub of TWM-30	To Do	Medium	Approval testing w/ automation routing #1
TWM-30		10572	Task	Approval testing w/ automation routing #1	Open	Medium

[John Funk]

Ah, true! I was thinking he was doing something with it, but the export should be fine. 

[Jack Brickey]

Hi @Diego MEDICS , when you export there will be a parent field. Are you not seeing this?