Hi! I'm looking to set up an automation rule that will mean epics inherit a custom field from their parent. The use case for this is; * We are using a custom hierarchy in which there are two levels above epics. * We would like to be able to change a custom field on the highest level and have that cascade down to the task level * There is an already an automation rule (see below) which works for tasks when the epics custom field is changed, however this does not work for epics and above Any advice on how to get this to work? Cheers

If it's not firing, then I would check the Rule Details to see if you have the box checked to Allow other rule actions ...

Issue is with the rule not firing, nothing to show in the audit log

Can you share a screenshot of one of the Initiative level issues? Also, when you say the automation does not work - what does that mean? That it doesn't fire? It gives you an error? Or it fires, no error, but it doesn't do what you want it to do? And can you share a screenshot of the audit log for that transaction?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Epic inherit custom field from parent

Andrew Martin_wpb520

Hi!

I'm looking to set up an automation rule that will mean epics inherit a custom field from their parent. The use case for this is;

We are using a custom hierarchy in which there are two levels above epics.
We would like to be able to change a custom field on the highest level and have that cascade down to the task level
There is an already an automation rule (see below) which works for tasks when the epics custom field is changed, however this does not work for epics and above