You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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 issue.issuetype.name 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then that is on the step/action where you do the linkage. Can you share that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, change that to Most Recently Created Issue and give it a test.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.