Automation to clone stories in an epic - for branch not working?

[Jezza Sutton]

I am trying to write some automation to clone an epic and all the stories but the branching part of my automation is not finding any stores/tasks in the epic to clone. I've used by For: Stories in Epic as well as some actual JQL that ought to return tickets. I thought the original For: Stories was perhaps confused by which epic it was looking at and picking up the new cloned and empty epic. Hence trying the JQL.

If I can get this to recognize the tickets in the epic then setting the epic link should be easy. The problem seems to be getting the for loop to see anything.

[Andrew]

Hi @John Wood!

It's not ideal resolution: use two dimensional gadget. For example xaxis - priority, yaxis - status, and when click status You will see result of ["your filter" and status = "clicked" ].

[John Wood]

If it showed the "was in" status I could live with this, but you still have to work out the numbers manually doing that, because the list is by current status.

That said, doing it did show me something else I should be reporting on :)

[Andrew]

Hm. This resolution worse, but :-)

Create filter for each status

project = CHANGE AND status was "Minor Reject (Peer)"

project = CHANGE AND status was "Minor Reject (Cloud)"

....

And add gadget "issue statistics" for each filter with "statistic type" = project.

[John Wood]

Yeah I might do this as a temp workaround, while i continue to find out if there is a "proper" way to do this (or an add-on).