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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

{{issue.issuelinks.outwardIssue.key}} not working during issue create

I want to send an email with a list of linked issues when a new issue is created. The issue being created has a linked issues (blocks).

I've setup a simple workflow - When issue created, then send email.

In the body of the email, I'm using {{issue.issuelinks.outwardIssue.key}} to list out the linked issues. But the linked issues don't show up in the email I get after the issue is created.

I'd appreciate any pointers to how I can get this to work.

1 answer

Hi @Rajendra Borde 

You are using the issue created trigger, so there could be a timing issue where the data is not yet available when the event occurs.  (This is a known problem for automation.)

The work-around to solve this is to add a Re-fetch action immediately after your trigger and before any other rule components.  This will slow down the rule and reload the issue before proceeding.

Kind regards,

Hi @Bill Sheboy 

Thank you for the the response. I've tried adding the Re-fetch action immediately after my create issue created trigger and before the send email component. Unfortunately it didn't work. I've tried adding several re-fetch actions blocks and multiple email components but no luck. If I change the trigger to transition issue, it works.

Would you please post images of your complete rule which does not work as you expect, and of the audit log showing the execution details?  That may provide some context to uncover what is happening.  Thanks!

Also, are you using Jira Cloud or Server/Data Center?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events