Maintaining Story Sort Order During Clone

Aaron Eden

I have a manually triggered automation that will clone an epic and all of its child stories (25 of them).   I would like the cloned stories to retain the same order as the ICSAUTO-1 epic they are being cloned from.

I attempted to do this by sorting my JQL result.  For some reason the stories still end up on the cloned epic in a pretty random order.

 

Automation

 

 

JQL Results - Showing the order inside the automation is correct

 

Stories on cloned epic (after automation execution)

 

Bill Sheboy

Hi @Aaron Eden 

Branches in rules which could-be-on-more-than-one-thing are executed in parallel and asynchronously, with no predictable processing order.

With an automation rule, I know two ways to enforce issue creation order, but neither will work for your scenario of 25 child issues.

1. In-line, creating each issue one by one.  This rule would be too long for the child issues.
2. Two rules, where the first one triggers a second rule, and the second rule uses an Incoming Webhook trigger to recursively call itself.  With 25 issues, this rule would exceed the looping limit of 10, self-triggered calls.

Outside of automation rules, there are likely marketplace apps for cloning, or you could build-your-own service which creates issues sequentially and call that service from a Jira rule.

Kind regards,
Bill