Running an 'expensive' JQL on the Average Time in Status gadget can consume resources and cause long running threads and can cause JIRA to become unresponsive.
Create a gadget on a test dashboard for "Average Time in Status"
Configure the gadget with the following settings:
Filter: that returns ALL issues
Statuses: select ALL status
Days Previously: 300 (which appears to be the maximum)
Refresh Interval: Every 15 mins
JIRA server CPU utilization spikes and accessing administration pages is unresponsive.
The below is an example of the size of an instance that has experienced this:
Is there some type of boundary limit or check that we can implement to prevent these 'expensive' queries from running?