Using JQL functions with enabled caching

By default, the plugin caches all closed sprint reports because, in most cases, it is a permanent entity.

if you cache on with using the JQL filter - "Time to resolution" < remaining ("2h"), the cached results can be expired immediately because the remaining time is not a static value and changes in time.

More examples of "fast expired" JQL expressions:

created <= -5d
changed <= -5d
"Time to first response" < elapsed("10m")

For all the above cases, we recommend switching off the cache feature.

More details about fast expired JQL functions: https://confluence.atlassian.com/servicemanagementserver/using-jql-queries-specific-to-slas-939926424.html

You can disable the cache feature in the settings at any moment with subsequence not achieving benefits using cache for reports which contain a large number of tickets, such as load speed increase.

Tip: When copying the JQL filter from another source, look around to spot whether a fast expired JQL function is being used.