Unable to open "Active Sprints" on Safari

Question

When clicking on "Active Sprints" in Safari no sprint is displayed.

I checked in the log and it could be this line (line 37052 in the prettified version displayed by Safari):

e = document.querySelectorAll("script[src*='batch.js'"),

in this file

https://{subdomain}.atlassian.net/s/{hash}-CDN/-egccmf/b/24/{hash}/_/download/contextbatch/js/greenhopper-rapid-non-gadget,gh-rapid,jira.project.sidebar,jira.global,atl.general,jira.general,atl.global,-_super/batch.js

that is causing the issue. The string passed to querySelectorAll() returns a result if there is a closing square bracket:

e = document.querySelectorAll("script[src*='batch.js']"),

As it currently is it throws an error when run in Safari. Chrome seems to accept this malformed identifier and displays the page, Safari throws an unhandled error and hangs.

Yelnar · Answer

I have same issue.

* Can you confirm the version of your Safari: 12.1 (14607.1.40.1.4).
* Is this problem happening to all of your Scrum projects or just on this specific one? All.
* Is the problem happening to other users too? Yes.
* Have you tried to clear your browser cache and access it in incognito mode? Maybe a browser extension could be causing the problem. Tried all.

Petter Gonçalves · Answer

Hello @Martin Baillie

Thank you for reaching out.

I tried to reproduce your issue in Safari 13.1 (15609.1.20.111.8), using both a Classic and Next-gen Scrum projects in my Jira Cloud test site, however, the Active Sprint is displayed just fine to me:

That being said, please provide us with the information below so we can further troubleshoot it:

* Can you confirm the version of your Safari?
* Is this problem happening to all of your Scrum projects or just on this specific one?
* Is the problem happening to other users too?
* Have you tried to clear your browser cache and access it in incognito mode? Maybe a browser extension could be causing the problem.
* I was not able to find the mentioned line in the file. Could you please provide us with the path you followed to access it?

If the steps above didn't help, we suggest opening an internal issue with Atlassian support so we can take a deeper look at the .HAR file of your browser and further troubleshoot the issue:

https://support.atlassian.com/contact/

Let us know if you have any questions.