Currently, there is a problem registered with bug : JRASERVER-77656: Viewing an idle browser tab on a Jira dashboard can cause many simultaneous gadget requests leading to high CPU or OOME (fixed in Jira Data Center 9.12.15, 10.2.0).

When a web browser tab with a dashboard is idle, the gadgets are not properly refreshed, even if the "Update every 15 minutes" setting is configured. Instead, they update only after the focus returns to the open web browser tab, and 15 minutes have passed.

This behavior is inconvenient because the business requires working on multiple displays, each with a different Jira Dashboard and gadgets. Since the focus is not on these tabs, the gadgets won't be properly updated.

Being able to configure the update frequency and/or priority individually may help to:

Avoid having all gadgets updated simultaneously, which can cause performance issues in the instance.

Allow Jira users to leave idle web browser tabs with different dashboards, knowing they will be properly updated.