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!


Get the issue key from project INF or PSE blocking the other issue from project CS

I am recently new in Jira Cloud and I would like to create an automation rule which will pick up the issue(linked issue) key from Project INF or PSE, blocking another issue from project CS, and write it into custom text field(Issue Blocked By) created.

Steps I followed:

-Created a custom short text field and linked this field to Project CS screen.
-I created a simple automation rule as seen in the attachments.
-The rule scope is for multiple projects(CS,INF,PSE)

it completes the automation rule successfully, but, on the screen, the custom field(Issue Blocked By) comes with "None"

Please let me know in where I am doing wrong?
Thanks and Regards


1 answer

0 votes
Kevin Lew _ServiceRocket_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Nov 09, 2023

Hi @Harun Ahmetbeyoglu

The automation that you currently have will need to have some improvement.

Firstly, It doesn't tell the automation which Jira issue to update. It should be the CS project issue for your case, but looking at the screenshot, it seems like the edited issue is PSE-473, the issue that trigger this automation. 

To overcome this, you can use the "Branch rule / related issues" for 'Destination issue' right after your IF/ELSE statement. This should tell the automation which issue you want to perform the action. 

Here is the documentation for your reference.

Second, the smart value that you should use to edit the issue field is  '{{issue.issuelinks.inwardIssue.key}}'. In your case, it should be inward

Here is the community post for you to understand the differences between inward and outward.

Here is a quick snapshot of how the automation looks like to achieve your use case:



Please let me know if this helps, and if this resolves your issue, please mark this as the answer. 



Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events