Failed to load remote issue because remote site is not linked

[Paul]

Hello,

I have the below script which is used to setup a remote link between two of our jira instances. The link is setup successfully, however it displays the following error.

When clicking on the link it does take me to the correct ticket, on the correct cloud instance. Also, a tunnel between the two sites has been setup and yet this still occurs. 

Can anyone help resolve this error so that it shows the correct ticket and description.

Script being used:

{
"globalId": "appId=abcdefgh-ijkl-mnop-qrst-uvwxyz123456&issueId={{webhookdata.id}}",
"application": {
"type": "com.atlassian.jira",
"name": "Jira"
},
"relationship": "Tempo Link",
"object": {
"url": "https://example.atlassian.net/browse/{{webhookdata.key}}",
"title": "{{webhookdata.key}}"
}
}

Thank you.

[Synaptics Tony Chang]

Hi @Paul @Akshithrekulapelli , I have the same issue and solve it by finding a real sample.

I figure it out by :
1. manual add a remote issue link to the same remote issue with standard feature

2. call the restful API : rest/api/latest/issue/[your local issue key]/remotelink and examine the return response.

3. Find globalID in the response. The globalID is constructed by appId and issueId parameters : 

where appId is the application link id, you can find it in the URL when you edit the application link;  issueId is the remote issue id. You can find remote issue id by restful API  ( https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get ).

[Marc - Devoteam]

Hi @Paul 

Welcome to the community.

Jira instances can be linked via setting up application links between the instances.

See documentation: use-applinks-to-link-to-atlassian-products 

[Paul]

Hi @Marc - Devoteam 

Thanks, and thank you for getting back to me. 

The application links have been setup and have been configured with direct access. To be sure this was not the cause, I deleted the existing connection and reestablished one between the two sites and tried the script again.

Unfortunately, the same error is present.

What is peculiar is that if I setup a remote link manually I am able to see the details of the target ticket and an error is not displayed. It only appears to happen when it is done via automation.

[Paul]

This is still an on-going issue. Can anyone help?

[@Akshithrekulapelli]

Even I am facing same kind of issue, did you got any solution?

[Marc - Devoteam]

Hi @Paul 

I suggest you to raise this as a bug at Atlassian Support.

They might see what is not resolving correctly, to have the link show.

They have access to all logging related to your instance.