Jira Export - Sorting and collating Epics and their Sub-tasks using Parent ID

[david-r]

Hi Community,

Background

We export data from our Jira Instance into csv format. Alteryx then cleanses and sorts this data into a manageable format for sprint planning/triaging.

We've applied various sorting criteria including Priority, Customer and Component, but ultimately we face the same problem, that is our Epics and their Sub-Tasks appear in random order rather than being collected together.

Use Case:

As a user I'd like to sort our export data so that Epics and their sub-tasks are grouped together.

See attached for an illustration

Left table = current behaviour

Right table = expected behaviour

Requirements:

Note the order is Epic followed by it's sub-tasks followed by the next Epic and then it's sub-tasks etc.

The data used for this sorting will be the two columns of data: "Parent ID" and "Issue ID".

Presumably we need to find any tickets with a "Parent ID" (primary key), find that corresponding and unique "Issue ID" and then list them in the order as described above.

Any remaining tasks (those without a Parent ID i.e. non-Epics) should appear at the bottom of the sorting order.

Note:

I've renamed the Summary and Issue Key solely for the purpose of making the requirements clearer, we can't use these columns for sorting as they would not be named in this format.

Thanks,

David

[afv2688]

Hello @david-r,

You could use this:

It creates a column to sort the data

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Regards

[david-r]

Hi afv2688,

Thank you but I've renamed the contents of Field1 just for the purpose of illistrating the problem (see note in the original post). Using this column for sorting is not an option as the contents of the column will be real data i.e. the summary of the issue.

The idea here is to use simply columns "Parent ID" and "Issue ID" for sorting. Not an easy one.

Thanks,

David

[afv2688]

Changed the logic a little bit. Lets see if it works now. I applied a second filter just to have the rest of the tasks ordered by the type. You can just tak it down if you don't need it.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Regards

[CassC · Accepted solution]

Hi,

This is a really interesting problem of creating hierarchical sorting across multiple fields.

I tried to build out a solution that I think meets your requirements, which I've attached here.

My final output doesn't quite match yours (my Issues are not sorted by the Sub Task number), but I think this meets the requirements you listed on what fields can be used.

Let me know if you have questions!

[david-r]

This is a great solution, thank you! Took a while to verify but it meets the requirements, great job.