How to get issue-key from linked Project in another instance

[Daniel Ruping]

I have access to two Jiras:
Project A: Jira Data Center

Project B: Jira Cloud

I can set up links between those two Jira instances and this works fine. 
I set these links manually which is also fine. Most of the time it's links "Ticket from Project B is blocked by Ticket from project A" using Create reciprocal link. 

Now I want to set up an automation in Project A which writes a comment to linked tickets in Project B. 
I am using web-hooks, which works fine. But I can't find a way to use {{issue.issueLinks...}} and all derivations because Automations in Jira A seem to be blind for Linked issues in Jira B. 
They don't even trigger an if statement "any issue links exist". 

I think(!) this is because of "Only issues from the above projects will be considered. You can change this restriction in the 'Rule details' section." - but I can't change this. And I don't really understand why I can't let it also watch over ALL linked issues and not only those from Project A. I'd just need the issue-key from the linked item to complete the webhook-url... but I can't. 

What can I do to bring this automation to life and also respect linked issues from Project B? 

[Matthias Gaiser _K15t_ · Accepted solution]

Hey @Daniel Ruping

the issue links to another Jira are not stored as usual issue links, they are stored as remotelinks. You can try to view the remotelinks if you go to the url: JIRA_BASE_URL/rest/api/2/issue/ISSUE-KEY/remotelink

You can find Atlassian's documentation about the remotelink REST API here.

What I'd recommend: You can use a send web request action in automation to get all the remote links for that issue. I'm not sure about the trigger though..

Cheers,
Matthias.

[Daniel Ruping]

thank you very much. This works :) 

Trigger would be "issue transitioned" and then I can check via Webhook, if there are any remotelinks. 
Sadly I can not do a "for-each" in Data Center as far as I can see, so I need to check if there are any elements in the json and then put as much following actions using get(0-n) as I think are sufficient. 

And as I need to send web requests during each iteration I also need to send the initial Web request as I can't store a JSON into a variable. :-/ But I think I can make it work now. Not beautiful, but will work. 

[Matthias Gaiser _K15t_]

oh no - I was not aware of the limitations on DC that there is no for-each loop :/

But I'm glad you can work out a solution now.

[Daniel Ruping]

yep it's pretty limited - you can only loop over issues. But in the end it will work as long as there are not too many external links.