Issue Browse Page Has Many Console Errors


I noticed today that Chrome is reporting issue pages as "Not secure" because the page references some resources using HTTP from a secure page. 

Not a big deal unless you're security paranoid.

When I looked at the console I see cross-origin errors, errors on AJAX calls, and many other errors. 

Is this something to do with a plugin we're using or is Atlassian not looking for errors on the client when they do their QA? console errors.pngpart-2.png



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events