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.

[Joshwa Marcalle]

would recommend a more graphical, simpler solution to this problem.

https://marketplace.atlassian.com/apps/1219348/hours-reports-for-jira?hosting=cloud&tab=overview

Its a cool addon that helps us determine when the estimations of the tasks have gone overboard. 

As far as JQL for this, I do not think it is possible to calculate as you estated but there is a field for this, its called workratio. So you can do this: 

workratio >100

[Bhavesh Shah]

Hi Thanks for the response.

I tried using workratio but the field only takes into account logged hours. I want to do logged + remaining <= Original estimate. Is there any such field?

[Scott Morris]

Ever find a solution here?

workratio catches issues when it's too late

Would be good to catch issues as soon as the remaining is increased (rather than decreased) with a new worklog

[kristina_petrosino]

Would also like a solution as "work ratio" takes into account 'time/estimate remaining' and we dont use that field, so it never calculates correctly for us. I want worklogged (or timespent) is greater than or equal to original estimate.