Linking issues on two different Jira instances

[Yurii Zhatkin]

Hi there, 

I have this case where I want to link issues between different Jira server instances. I created application link and the manual linking works as expected, with the selection of the server to and issue to which we gonna link:



Though, when I am using Jira automation and creating issues using webhook, the issue linking does not work in Automation.
Here is the part of my webhook rule: 

The smartvalue {{webhookData.key}} does not work in the automation rule, because the rule trying to find the value in the local Jira instance and not the remote, which is logical. So there should be a way to specify a server (Jira instance) where the value should be attributed, like the selection we have when manually linking issues. 

Maybe it would be possible to use json codes for this? Any ideas?

[William Zanchet [Atlassian] · Accepted solution]

Hi Daniel,

I was able to do a research and I could see that IE11 is supported as you can see here:

https://confluence.atlassian.com/jira/supported-platforms-207488170.html

Do you know when this problem started to happen? You might want to try to access IE through the Safemode and see if you can replicate the same problem. Also, try a different network environment to see if that is the issue.

Cheers,
WZ

[Deleted user]

Can I ask why this answer was marked as "the" answer? I've got a user on IE 11 that also has issues and we're on JIRA 7.1.2.

What I mean is: simply pointing to the docs that say IE 11 is supported doesn't really solve the problem...

[Stephen Sorrell]

Not sure if this will help but it seemed to clear up issues with JIRA and IE for us.  Under Internet Options, click the Advanced tab and then under the Security settings, make sure the 'Enable DOM Storage' is checked. 

[Abhinav Chaturvedi]

Hi,

We are using JIRA 7.12.3 but it's not working properly with IE. It works perfect with Chrome.

Tried everything that is mentioned here but no luck .

[Jaakko Linnosaari]

1. Open DevTools in IE11 (Press F12)
2. Check Console for parsing errors
3. See what app is responsible (Check the source code by clicking on the error)
4. Disable app and report to app vendor
5. ?
6. Profit!

[Brett Trigg]

Same symptoms on Service Desk with the following browsers:

Microsoft Edge 41.16299.248.0

IE 11.309.16299.0

[Karen St Germain]

We are having the same issue with JIRA software and service desk (cloud)

[it info]

Hello,

we have also no luck with IE after the Upgrade. I can see the Top Panel but the Page is empty, have you found any solution?

[Stephen Sorrell]

I'm also in the process of testing JIRA in IE11 for a planned upgrade and so far not having any luck getting JIRA to work in IE. I've tried multiple settings changes to Security rules and still don't seem to be making any progress. Were you ever able to resolved your issue?