Upon epic update, push field value to stories and subtasks

[Dennis Decoster]

Below you'll get an idea of what I'm trying to accomplish...

When in an epic either or both the fields are updated, then these values should be copied to the underlying stories and subtasks too.

I have discovered that:

1. jira automation cannot manage more than 1 hierarchy level, so 2 rules are needed
2. the automated update of the story by rule 1, is not picked up as an event by the 2nd rule, so I can't chain them together

Now as subtasks can't  seemingly pull info straight from the epic, and the parent (aka story) is not an usable event, I am stuped on how to fix this.

Previous downward automations like cancellations were never a problem to set up...

[Dennis Decoster · Accepted solution]

problem solved. forgot to check the box to have the 2nd rule trigger from the 1st....