Replacing Linked issue with Epic Link if Epic link empty in child - EMAIL RIGGER yes/no

[Mateusz Janus]

Hello Brothers and Sisters,

I have a small automation which works perfectly. When user links to EPIC any TASK with link relation "is a paret" then i am checking if TASK has EPIC LINK = null. If yes then I update EPIC LINK of TASK with EPIC issue key.

What I am looking for.

I want to inform users in case when:

1. EPIC LINK was null and NOW its updated

2. EPIC LINK was NOT null so automation could NOT provide new value

What i am thinking is trigger after GREEN CIRCLE. It means if condition is MET send email1

If condition is NOT MET send email2. Sounds simple but i cannot figure out how to build such condition...

[Arkadiusz Wroblewski · Accepted solution]

Hello @Mateusz Janus 

You need two branches:

one for “Epic Link is empty → set it → send Email 1”

one for “Epic Link is NOT empty → don’t touch it → send Email 2”

What to change in your rule

At the point where you currently have Compare two values ({{issue.Epic Link}} equals Empty):

Replace it with an IF / ELSE block (or add ELSE if it’s already an IF block).

IF {{issue.Epic Link}} equals Empty
→ Edit issue fields: set Epic Link = {{EPICID}}
→ Send Email 1 (updated)

ELSE (means Epic Link was not empty)
→ Send Email 2 (not updated)

Short email text you can use

Email 1 (was empty, now updated):
Epic Link on {{issue.key}} was empty and is now set to {{EPICID}}.

Email 2 (already set, not overwritten):
Epic Link on {{issue.key}} is already set ({{issue.Epic Link}}). Automation did not overwrite it.

If your DC version doesn’t show an ELSE option, do the same as two separate rules: one with condition “Epic Link is empty” (update + Email 1) and one with “Epic Link is not empty” (Email 2).

Hope it helps. Have a great Day :)

[Mateusz Janus]

HI @Arkadiusz Wroblewski ,

it was exactly my problem. My DC version has no ELSE option xD. So now its clear, have to have 2 automations. thanks

[Arkadiusz Wroblewski]

@Mateusz Janus 

You’re welcome. Regarding different DC versions: if your version doesn’t support the newer solution, just split them into two. 🙂