Linking the Jira issue from Bitbucket doesn't work

[Galya Bogdanova]

We have Jira integrated with a Bitbucket repo. After a commit, the Jira issue shows the reference to the repo. Clicking on the links to Bitbucket from the Jira issue works fine. In the reverse situation - clicking on the link to the Jira issue from Bitbucket worked fine initially, but several months ago something went wrong and now it's not working any more for me.

First a dialog appears "Log in to JIRA to see this issue". After clicking on the Login button, another dialog appears "We couldn't connect to that issue. Make sure that this issue actually exists in that project. If it does, try again in a few minutes. If you still can't link to the issue, contact your JIRA admin."

Bitbucket - https://bitbucket.org/loyaxandroid/loyax/

Jira - https://loyax-loyalty.atlassian.net/projects/LXD/issues/

What could be done to fix it?

Regards,

Galya

[Daniel Carter]

Same issue here.  The integration has been broken for like a year, when will this get fixed?

[Daniel Carter]

the 'middle click' (open in new tab) workaround works for me.

[Mark de Bont]

Please be sure to check your application are correctly configured

[John Busciglio]

I have been digging around the documents to find out exactly what this means. "Correctly Configured".  I also have a new Jira/Bitbucket cloud to cloud integration and followed the documentation.  I can see that I create branches from Jira, however, I have no link back to Jira from Bitbucket. 

I would love to understand how I can have half of this working and the other half not!  

Waiting to be able to see as the OP says,

"clicking on the link to the Jira issue from Bitbucket".

I've yet to see that link in Bitbucket

[Dylan Diamond]

Any update on this? I'm experiencing the same issue. 

[Jeff]

I would appreciate an update also. We have some employees experiencing this, it only started happening since the new year. Short term fix is to clear browser data, but the issue will reoccur again within a day or two.

[Ernest Koe]

having the same issue

[Ernest Koe]

seems to be a cross-site scripting prevention issue for me, if you are using safari, try this https://bitbucket.org/site/master/issues/17536/on-the-safari-browser-bitbucket-is-not