I want to write an automation rule that triggers automation then looks up children of that issue and runs the same automation on the children of that issue.
I know I am way out on a limb here, but has anyone done something similar? Dealing with initiatives otherwise I would use script runner and its epic functions, but higher tranches of tickets don't have the same support.
See the attached image for what I want the automation plan to be.
Hello @Joe Mabus
This post recommends that you use Advanced Branching with a JQL statement to get the issues (instead of a Lookup Issues action) and then within the branch you can edit the field(s) in the found issues.
(credit to @Daniel Alonso )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.