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

Link issues based on field contents Automation for Jira

I have a project where 2 different issue types use the same field.  Is it possible for me to create an automation that will look at that field and link the issues if they match?

1 answer

1 accepted

0 votes
Answer accepted
John Funk Community Leader Sep 02, 2020

Hi Chris,

Yes, you should be able to do that. 

Use the Condition for Advanced compare something like this:


The initial trigger could be Issue Created or Issue Updated.

And instead of customfield as in my example, use or issue.issuetype

@John Funk , thank you for the fast reply!

I have tried what you suggested but perhaps I have done something incorrectly.

I get an error that the issue is trying to link to itself.

2020-09-02 14_44_54-Project automation - ValJira USA.png2020-09-02 14_45_31-Project automation - ValJira USA.png

John Funk Community Leader Sep 02, 2020

Then that is on the step/action where you do the linkage. Can you share that? 

Here is the screenshot of that.  I think I see what the issue is but I do not seem to have enough options of what to link to.  Is there another smart-value that I can use?2020-09-02 15_57_11-Project automation - ValJira USA.png

John Funk Community Leader Sep 02, 2020

So, change that to Most Recently Created Issue and give it a test. 

This is the new error.2020-09-02 16_12_49-Project automation - ValJira USA.png

John Funk Community Leader Sep 02, 2020

You might need to do a Re-fetch action after the issue is created as I am not sure how your are populating the CAPX Project Number field. 

It would come before the Compare. 

The CAPX Project Number field is populated in the portal when the user submits the ticket.  

I tried the re-fetch action but unfortunately got the same error.

2020-09-02 16_31_46-Project automation - ValJira USA.png

John Funk Community Leader Sep 02, 2020

What is the key of the existing one it should find to link to? Is it the same project? 

Try creating a Branch (purple one) and using JQL there.


Use the project of the exiting issue where I have HROPS.

Then notice the change on the Link going under the Branch and changed to Trigger issue. 

Like Chris Brewer likes this

@John Funk , that worked!!!  Thank you so much!!!

John Funk Community Leader Sep 03, 2020

You are very welcome!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events