Issue URLs do not react to being clicked on in Jira Service Desk (server) in any browser

[Zena Jones]

We had this issue on 3.11.0 and have just upgraded to 3.11.1. Still the same issue. Issue URLs can be accessed from the dashboard. But not from within the "Assigned to me" queue. You can right click on an issue URL and ask it to open in a new tab, which it does successfully. 

But we get absolutely no response when clicking on the URL. If I hover over the URL and take note of it and enter this into the address bar, I can successfully open the issue and see everything and do everything I need to do. 

Any ideas on how to fix this? This would be appreciated. Cheers. 

[Boris Berenberg - Atlas Authority · Accepted solution]

Take a look in your Developer Tools Javascript Console in Chrome. See if there is an error there. I would especially look into any custom JS you may have added to the system or any third party apps. Try disabling them during a maintenance period and confirm that the issue continues to reproduce.

[Zena Jones]

Hi Boris... thanks for the prompt response.

Found this...

VM815:1 Uncaught SyntaxError: Unexpected token u in JSON at position 0
at Function.parse (<anonymous>)
at e.initialize (batch.js?healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jira-nps-enabled=true&jira.create.linked.issue=true&locale=en-AU&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&sd_operational=true&user-logged-in=true:5457)
at e.f.View (batch.js?locale=en-AU:1329)
at new e (batch.js?locale=en-AU:1342)
at g (batch.js?healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jira-nps-enabled=true&jira.create.linked.issue=true&locale=en-AU&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&sd_operational=true&user-logged-in=true:5457)
at HTMLDocument.<anonymous> (batch.js?healthcheck-resources=true&is-server-instance=true&is-system-admin=true&jira-nps-enabled=true&jira.create.linked.issue=true&locale=en-AU&nps-acknowledged=true&nps-not-opted-out=true&richediton=true&sd_operational=true&user-logged-in=true:5457)
at HTMLDocument.dispatch (batch.js?locale=en-AU:107)
at HTMLDocument.h (batch.js?locale=en-AU:99)
at Object.trigger (batch.js?locale=en-AU:104)
at HTMLDocument.<anonymous> (batch.js?locale=en-AU:120)

[Boris Berenberg - Atlas Authority]

Like I said, I would try killing third party apps one by one to see if one if them is interfering. I would also look in your announcement banner to see if you have any custom code there.

[Zena Jones]

Hi Boris

Thank you so much for your help. You were on the right track and it was a 3rd party add-on that was causing the issue. I've disabled this add-on now and will forward the error that I posted above to them for their review. 

Cheers. 

Zena.