I'm trying to create an automation that will email the Epic's assignee when an issue is either added or removed from it.
The closest I got from that logic was with the automation below:
However that automation is never triggered. When I check its Audit Logs, that's what I see:
Can anyone help me figure out where the mistake is? I tried creating an issue without epic and adding it to an epic, trying creating an issue directly from the epic screen, etc etc, but nothing seems to trigger this automation (despite it being active).
Hi Andre - Welcome to the Atlassian Community!
You won't be able to use the Parent Link field for that - that field is for hierarchy stuff above the Epic. And Epic Link field is not available to choose for Field Value changed.
Take a look at this previous post and then the section from the Post in 2022 for some guidance.
Hi @John Funk thank you for the tip!
After reading this blog post (Upcoming changes: 'epic-link' replaced with 'parent'), I got the impression the smart value Parent was a "superset" of Epic, in other words, it'd include both Parent (in case of sub-tasks) as well as Epic.
I changed the automation trigger and added two conditions. One that matches when the epic link changes from empty to not empty and another condition matching the opposite case. Like so:
The automation now, successfully triggers on both cases (Audit Log indicates "SUCCESS" and email sent).
However, I'm not getting the email (checked also my spam box). I understand the issue could be on our email provider, but we use regular GSuite for emailing and I believe no special security rules regarding excluding JIRA emails.
Any idea where else I could look for the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you email the user or a field value (like Reporter or Assignee) instead of an email address to see if that works?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.