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!


Linking in Plans does not trigger "Issue Updated" automation rule.

Michael Wu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 20, 2023

We have a complex structure in Plans, I have a rule to copy certain field values in "Child" issues when I link an Epic to an Initiative.
When I link in Plans, the Epic is updated with new "Parent Link" value, but the Initiative (in this case the Parent) has no update (even issue history does not show this change) and therefore does not trigger the rule with "Issue Updated" trigger. I need the Initiative (parent) to be the trigger issue since I am using "Copy field value from trigger issue" to edit the Epic (child). I need this to be the case because if I use the Epic as a trigger then copying values using {{issue.parent.customfield_xxxxx.value}} and {{issue.Parent Link.customfield_xxxxx.value}} does not work.

I have a workaround already which involves two rules and works as follows:

Rule 1: Issue updated > IF "Parent Link" is not EMPTY > Branch Rule JQL: issuekey = {{issue.Parent Link}} > Add comment

Rule 2 (Allowed trigger from other rules): Issue commented > Branch Rule JQL: "Parent Link" = {{issue.key}} > Edit Issue: copy fields.

BUT these don't cover cases where links exist and the field values are changed, I will probably need another rule for it.

All of this could be avoided if the parent was updated when linked through Plans, does anyone know why linking through plans does not update the parent? or a way to trigger the update event?


1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 20, 2023

Hi @Michael Wu -- Welcome to the Atlassian Community!

That seems to be a known issue for the Cloud and Server versions of automation.  You may vote for / watch this item (and the linked ones) here:

For now I believe your work-around is a good long as the comment is specific enough and there is no human "tampering" with the comment.

Kind regards,

Michael Wu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 22, 2023

Hello @Bill Sheboy thank you! voted and watched!!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events