Automation for JIRA #003 - Epic linking

Guys from a Marketing deparment at our office wants clarity and order in their Jira kanban board.
Nice.

I wrote two new automations for them which are semi-complex but very interesting. I will discuss and share them below. The problem was to “sort issues” and always link them with an appropiate epic. When an issue is added (a task or a story), with a specified Atom (Atom is the unique specific name for the project) then create epic link to the appropriate Epic.
Ok, it sounds very simple but there is no such easy way to get there, plus I had to minded few exceptions.
The whole automation was divide into two.
The first one:

This automation is doing a linking thing while an Epic exists and when there is no Epic with a specific Atom then automation is creating it in the first place.

The Second one is doing “epic linking” with smart value {{destinationissue}}.

Why this automation can not be done in the one process? The answer is: The smart values can not be used in the JQL condition.

There are three if-else conditions. First one checks if there is story from issue labeled “releaseprocess” (the one from service desk), another condition checks if it is a story with the appropriate {{destinationIssue.issueType.name}} and the last one is for a task.