Comments
-
Hola @Sandra Perez El desencadenador tiene que ser manual como se muestra en la segunda imagen del post original. El desencadenador manual sirve para llamar la ejecución de la regla dentro de alguna incidencia y tomar esa incidencia como referencia para todos los smart values usados dentro de la regla. Si necesitas más…
-
Hi @Derick You can manually write the smart value in the field and click on it to use it: I hope this has helped solve your questions. BR, Jorge
-
Hi @Jo-Lee Bertrand Thanks for your comment. Going forward you can use the Parent field. I've updated the main post to show this information. BR, Jorge Herrera
-
Hi, @Coach Kevin; thanks for trying this workaround. By design, the branch executions for Jira Automation rules are done in parallel: * Ordering of branch executions Because of this, it's not possible to guarantee that the cloned issues will be in the same order as the original ones. There is a feature request to support…
-
Hi @Michelle Herschell Thanks for trying this solution. If the condition looking for "key:" is not met. it cloud be possible that the string is not added in the first rule: This part is important to let the 2nd rule know the original issue where each Epic child was cloned from, so the 2nd rule can find and clone the…
-
Hi @Kelli Frattini-Adams, I hope you are having a great day! I see the regex to extract the original issue is not correct, I should be: smart value: {{issue.summary.replaceAll("(.*key:)","")}} And as per your snapshots, I see you are using the one to fix the summary (which is basically opposite to the other smart value).…
-
Thanks a lot for your feedback @Yatish Madhav. I hope you and many of our customers can benefit from this solution. BR, Jorge Herrera
