Automation - How comment linkedIssues

[Julian Governale]

Im setting up an automation rule to do the following.

• On create issue check to see if other issues have a matching customer number (working)
• Link issues with matching customer number back to the created issue (Working)
• JQL for issues with same Customer Number (working)
• Comment on issues returned in the JQL indicating the newly created issue has the same customer number, add link to trigger issue in comment {{triggerIssue.key}} (working)
• Comment on newly created issue with issue keys to linked issues (Not working)

I cant get the last piece to work which is the newly created issue that kicked off the automation rule to have a comment posted indicating the other linked issues have the same customer number.

Ive tried multiple ways using the following smart value but none post the issue key into the comment - {{issue.fields.issuelinks.outwardIssue.key}}"

Any help would be appreciated.

Step 1

Step 2

Step 3

Full Comment from step 3

[Alexander Pappert · Accepted solution]

In step1 you create the links:
link type = ?

in step3 you try to geht the key of these links:
link type = outward

see also https://blog.codebarrel.io/how-to-use-the-linked-issue-trigger-in-automation-for-jira-1616b68c2d6e?gi=6ebd378e4ca3 

{{issue.issuelinks.outwardIssue.key}} 

can you use the "reload" function befor step 3?
maybe the link is there, but aotomation does not see it because you just created it

[Julian Governale]

Thanks for the response.  I added the re-fetch action but same result, was not able to pull the linked issues keys into the comment.  I tired the smart value you indicated as well but didnt work.  i was using outwardIssue in my smart value initially as that's where the data resides within the array when i run the end point from postman https://{{host}}/rest/api/2/issue/<issueKey>?expand=names

Im using the duplicates linkedIssue option but can really use any. Screen shot of newly created issue with the same customer number, blank linkedIssue key in comment. 

[Alexander Pappert]

mabe this is helpful

https://blog.codebarrel.io/how-to-use-the-linked-issue-trigger-in-automation-for-jira-1616b68c2d6e?gi=6ebd378e4ca3 

[Julian Governale]

@Alexander Pappert The destinationIssue smart value didnt work but it lead me to another thread by searching some key words fund in there which lead me to the smart value solution.  In essence, i didnt need the issue.fields step and once I removed .fields, I got the results I was looking for.   If you update your initial solution with a link the codebarrel article you had, i'll mark your answer as the solution.

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Can-I-link-issues-with-Automation-for-JIRA-when-I-create-a-new/qaq-p/2712 

Only caveat im seeing is that only the last issue has an active link in the comment. 

This ticket has the same customer number as {{issue.issuelinks.outwardIssue.key}} 

 

[Alexander Pappert]

@Julian Governale 

I updated my initial post

[JD]

Hey @Julian Governale ,

I don't know a lot about the outwardIssue smart value but you could try an issue lookup action and comment with the smart value. 

The smart value provides a list of issues as the result based on a JQL search. You can use the issue key and Jira should automatically convert it to a link (note I put a space after the {{key}} and the {{/}} ).

{{#lookupIssues}}{{key}} {{/}}

- John

[Julian Governale]

Thanks @JD this is great as it add's links to all the Keys! Much appreciated. 

[Mauricio Heberle]

Thanks !!