...
When users has multiple gadgets on a dashboard, multiple reloads are required for the gadgets to display properly.
The console logs shows that a large amounts of request results in 429 (Too Many Requests)
...
Root Cause
This There is a known issue for Jira Cloud , there is a limitation where the REST API calls can only call 100 requests each time.
When loading Dashboard page, if gadgets are present the browser will make a high number of requests to server for the webresources (CSS, JS) to load the results so the number of web requests can significantly increase dependent on the higher number of gadgets.
For the (failed) status requests, this is likely due to the chrome not being able to handle the large amount of requests resulting in the error If there are many gadgets on the dashboard page, it may cause the browser to make a lot of requests (for CSS and Javascript files).
Some browsers like Chrome has a limit on the number of requests per page, so it will result in the "429 (Too Many Requests)" error.
...
| Tip |
|---|
You may verify the number of requests going to the Network tab in the Developer Tools. |
Possible Workaround
Reload the dashboard again so that it can reuse the cached resources
Reduce or consolidate the number of gadgets on the dashboard (We recommend not exceeding 8 gadgets)
Refine the JQL filter to reduce the scope of issues retrieved