Automation rules run successfully, however nothing is changing in the ticket

[Ori Gal]

Hello,

I've created a simple rule: IF a specific field in an Epic changes, apply this change to all children's work items.

Everything seems ok and I get a SUCCESS result in the audit log (with a list of all the tickets that have changed due to the rule), but nothing actually changes in the sub-items (i.e. children).

Any idea what could be the issue?

[Filipi Lima]

@Stefan Salzl idea should work - changing from:

• Copy OKR (test) from Current Issue

To:

• Copy OKR (test) from Trigger Issue

For others that face a similar problem, an alternative that doesn't require the rule being triggered by the Epic is to use:

• Copy field from Epic Issue

This way even if the rule is triggered directly by the Story, it can fetch information from the Epic. There's also another option of copying from parent which is useful for sub-tasks.

Cheers!
Filipi Lima

[Bill Sheboy]

Hi @Ori Gal -- Welcome to the Atlassian Community!

Yes, and...to the the answer from @Filipi Lima :

This rule is triggered on changes to your OKR (test) field, and that can lead to changing the sibling issues' field (with the same parent Epic)...and so could eventually re-trigger the rule, subject to rule execution performance.

I recommend adding a condition before the edit, and only editing the field if it does not already equal the value from the trigger issue.  That will help halt any looping, when it occurs.

Kind regards,
Bill

[Ori Gal]

Thank you for your quick response and help.

I followed your advice but there seems to be an issue, as I get an error message saying: "Additional fields contains invalid field(s) in 'update' or 'fields' section: Custom Field Name"

any idea why is this happening?

[Bill Sheboy]

Hi, @Ori Gal 

If you look at that error message, you will see the cause: there is an invalid field name in the JSON for the advanced edit, "More options".  Please remove that section, or change it to be the field you wanted to edit.

As you are already updating the OKR (test) field earlier there is no need for that field in the JSON.

Kind regards,
Bill

[Ori Gal]

Hi @Bill Sheboy ,

I managed to make it work. thank you everyone for your help!

Best regards,

Ori

[Stefan Salzl]

Hi @Ori Gal  — welcome to the community!

as the rule branches for stories if the epic the setting „current issue“ is taking the stories of the epic into account. So to say „copy from current issue“ is trying to copy the story‘s own value of the required field. If you‘d like to copy the epic‘s field value after it has changed there try to use „copy from trigger issue“. That should then copy the value from the epic to the stories.

Please let me know if this works.

Best
Stefan

[Greg Williams]

Just wanted to put a note in this thread that I was having a similar issue with my automation (Needing to copy the "Components" of a Parent into the Child tickets) and I had the automation field set to "Current Issue". When I changed to "Trigger issue" the automation worked like a charm. Thanks to @Stefan Salzl for the tip!

[Stefan Salzl]

Hej @Greg Williams 

good to hear it was helpful. Thanks for

the kind feedback 🙏🏼

Best
Stefsn