Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Using Epic Link for field value change trigger?


In order to get around Jira's inability (refusal?) to link subtasks to epics out of the box, I've successfully come up with an automation for when new subtasks are created under an issue belonging to an epic.  The automation adds a new type of issue link of "has epic ancestor of" between the sub-task and the parent issue's epic.  (Screenshots below.)

automation 1.png automation 2.png

However, I'm trying to come up with the automation that will create or update this issue link if the existing sub-task's parent issue is added to an epic for the first time, or added to a different epic.

My instinct for the trigger would be to use "Field value changed" and have the field to monitor for changes be the Epic Link, but Epic Link doesn't appear as an option:

field to monitor.png

I can type in Epic Link and save the rule without receiving an error message, but the trigger doesn't appear to get set off.

Any suggestions on how to use a field change of epic link as a trigger, or another way to go about this?

2 answers

1 accepted

0 votes
Answer accepted

Never mind - I see that this is a bug that has been fixed in a later version of Jira (I'm on 8.2.4).  Leaving this question here in case anyone finds the automation for adding an issue link between a subtask and its parent issue's epic useful.

@Lucinda Stroud  You may use combination of Trigger and Condition:



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events