Automation for Jira - "Edit Issue Fields" action does not trigger the native Jira field edited event

[Tomasz Skalniak]

I have two Automation rules:

1. After Initiative.duedate changes, update all the "Initiative contains" epics duedates
2. After Epic.duedate changes, update all the epic issues duedates

Both rules work:

1. If I manually update the Initiative duedate, the duedates of all linked Epics are propagated from the Initiative
2. If I manually update the Epic duedate, the duedates of all the Epic issues are changed.

However I would like the two rules to work together. If "rule 1" changes automatically the duedate of the linked Epics, the Epic duedates are changed, so "rule 2" should be fired as a consequence of running "rule 1".

Unfortunately the "rule 2" is only fired if I change the Epic duedate manually. It seems to me that the "Edit Issue Fields" Action which I have used to change the Epic duedates in "rule 1" doesn't send the right, native Jira field.edited event (or something similar).

Thanks for any advises, and all the help.

[Raynard Rhodes · Accepted solution]

Can you take a screencap or your automation?

[Tomasz Skalniak]

[Raynard Rhodes]

Unless you have an automation to change the due date automatically, then this will trigger when it's manually changed. Both rules seem they need to be manually changed...

Are you attempting to automatically change the due date?

[Tomasz Skalniak]

I want to automate how the due dates are managed under following conditions and requirements:

Structure:

1. There are Initiatives with the due dates.
2. There are Epics with the due dates.
3. There are Tasks/Stories, and other issue types.
4. Initiatives are connected with Epics via the "initiative contains" link relationship
5.  Issues (e.g. Stories) are connected with Epics via the "Epic Link" field

Top-down process of propagating the changes of Initiative.duedates (to be automated):

1. If a Initiative.duedate is changed (manually), the related Epics.duedates should be automatically propagated from the Initiative.  // in my case: "rule 1"
2. As a consequence, the Epics.children issues duedates should also be changed (propagated from the Epic)  // in my case: "rule 2"

BTW. In the future I want to also automate the down-top duedates propagation. e.g. from Task to Epic, to Initiatives. However let's leave it for now.

[Raynard Rhodes]

Ah, I see. Essentially when you manually change the due date in rule 1, everything else should be automatic.

It's odd the way you have it seem as if it should work. When you look in the audit logs does it give an error or does it act as if it never ran in the first place? (For rule 2)

[Tomasz Skalniak]

After looking at the audit logs, it seems that the "rule 2" is never ran as a consequence of running the "rule 1". It is started after changing the Initiative value, but on the first condition it stops. And this is understandable and ok. What is expected, but doesn't work, is to start the rule after/as a consequence of executing the "rule 1". It seems it is not possible to do it, is it?

[Nick Menere]

Hey Tomasz,

But default rules don't trigger other rules. This is done to prevent loops.
In order to allow your rule to be triggered by an edit in another rule, select the following option on the rule details page: "Allow rule trigger"

Hopefully that was the issue.

Cheers,

Nick

[Tomasz Skalniak]

Hey Nick,
thanks, I have missed that option. Now it works as I have planned. Thank you!

Cheers,
Tom