Currently, when an issue is added to an epic in next-gen, Jira fires the Issue Updated for the child issue, but not for the Epic Parent. This is causing only one automation rule to be triggered for the child but not for the epic, even though the Epic's history indicates that Epic Child was updated.
(Epics in classic are unaffected.)
- Create an automation rule with an issue updated as a trigger event.
- Add Issue to an Epic
- The rule is triggered once for the child, although the parent was updated as well.
Adding Stories to Epics should trigger the rule for both issues.
Only the Story throws the rule once.
Epics in next-gen
Automation for jira