JQL function requirements() must have a mechanism of preventing too much data to be loaded

For huge instances, a call like this issue in requirements(UNCOVERED) could represent a huge amount of issues.

Xray already optimized this to use only the ids of the issues, but as this JQL may have to load the hierarchical structure of issues, if there are many issues, calculations will not end in the timeframe of 60s (timeout of Jira JQL screen call) and the user may be tempted to search again when in fact the calculations are still being made in the backend.