Are you a developer running in "dev mode"?
Do not start in "dev mode", i.e. check the system property "-Datlassian.dev.mode" or execute System.clearProperty("atlassian.dev.mode") at a Java breakpoint. This will however disable the development features.
If you are a regular, non-technical user, then I would suggest to check back with your administrator that they didn't start Jira in dev mode, which is visible in the "System info" administration of Jira (search for -Datlassian.dev.mode).
Thanks Adrian, that was really it. Batching being turned off causes a flood of requests which hit the Chrome limit at some point. Karol, I can suggest is removing "view" and "selectedIssue" query paremeters from the URL. That reduced the number of assets that get loaded
Chrome 75 is loading agile bords fine. Downgrading chrome is not a solution but working workaround :) . Anyway some kind of permanent solution to the problem is needed on Jira side or on the chrome side like request to change chrome async js loading by increasing limits or introduce some kind of async request queuing ?
Does anyone know in which version of chromium this is fixed. That translates in to which version of Microsoft EDGE :).
I have looked in the chromium issue list but not found any details.
I am seeing this problem in a Dashboard using multipile, 10+, road map gadgets. I am on a corporate windows platform with EDGE version 86.0.622.69.
It looks that the problem is still present in Edge and latest version of Chrome.
Not all gadgets are loading on a Jira Board and after refreshing the page, the missing gadgets are loaded correctly.
@Nic Brough _Adaptavist_ Do you have the reference to the Chromium bug you mentioned more than 3 years ago? :) Just want to make sure this is the exactly same issue as one reported initially and if there is any progress in fixing it.