Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Email notifications for when issue links are added


Normally when a user edits an issue, the watchers are notified. However, I've come to realize this doesn't work for linked issues - if someone links issue A to issue B, I don't get a notification for either issue, even if I'm a watcher on both of them.

Jira support suggested I create an automation that does this. I'm getting stuck on figuring out how to show what new links were added using smart values. I can access the entire list of issue links using {{issueLinks}}, but I just want the new issues that were linked.




I tried using the {{fieldChange}} smart values that are listed on this support page, but none of them seem to work for me.  (That section of the page also has some typos, so I'm not sure how much to trust it):



Does anyone know how I might get just the issue links that were added, not all of the issue links?

I'm also hoping to set up a similar automation for when issue links are deleted.


1 answer

1 accepted

3 votes
Answer accepted
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 01, 2022

Hi @Jackie Scanlon ,

Guess this could even be solved in a much simpler way using the destination issue smart value.

This will only refer to the "linking" event and takes only the source and destination issue into account, so the rule can directly refer to the needed issue.



Ah, that's perfect! Thank you so much!

Like Stefan Salzl likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events