Sorting Hiearchy in Structure Automation instead of Key

[Marcus]

I've added a Automation Structure that opens all my project Epics, stories and tasks. It lists them in a good way with childs underneatch their parents. I also removed all duplicate. 

But I've seen an issue where stories/tasks/epics created with a higher/later project key ends up higher in the hierarchy even if the task is a child of another. Is it possible to fix this ?

Example in the automated strucure is like this:

ProjKey-001 Child to Parent

ProjKey-002 Child to Parent

ProjKey-003 Parent

ProjKey-004 Child to Parent (newest created issue, created after parent)

The hierarchy in Automation becomes:

-Projkey-004 (child)

      -ProjKey-003 (parent)

             -ProjKey-002 (child)

             -ProjKey-001 (child)

But I want it like:

 -ProjKey-003 (parent)

        -ProjKey-002 (child)

        -ProjKey-001 (child)

        -Projkey-004 (child)

[Stepan Kholodov _Tempo_]

Hello @Marcus 

It is possible to sort issues in a structure by many different parameters in both ascending and descending order. You can do it by adding a Sort Generator. You can try applying sorting by Key or by the Created date, if it makes sense, and also change the order to see whichever setup works better for you.

If the sorting doesn't give you the result you need, then we'll need more details about your structure to understand the context better. In this case, please reach out to us directly at our support portal and we'll get back to you shortly.

Best regards,
Stepan Kholodov
Tempo