Filtering Tests in "TODO" status inside a Test Plan causes frontend timeout and eventually OOM

Steps to reproduce:

When users attempt to filter for Tests in TODO status within a Test Plan, like this:

It will generate a request such as this:

issue in testPlanTests("PROJ-123") AND (issue in testPlanTests("PROJ-123" , "TODO"))

In some cases causing the frontend request to timeout, with the message "An error occurred while processing table data" being displayed under the 'Tests' section of the Test Plan issue:

This issue does not occur with other statuses (e.g., PASS, FAIL, EXECUTING), which return results normally.

After investigation, it seems that:

• The request is correctly formed and processed on the backend.

• However, since TODO status is not indexed in Lucene, in some cases it takes longer to process the request, resulting in a timeout on the frontend.

Expected behavior:

Filtering by TODO status should work as efficiently as other statuses and not result in timeouts.

Actual behavior:

In some cases, the user will be are unable to filter by TODO status in the Test Plan, which limits the usefulness of the Test Plan UI for tracking pending work.

Note: this issue is not consistent, as it won't affect all Test Plans or all users. However, processing requests with TODO status always take longer, and depending on the Test Plan issue and the user making the request, it can lead to timeouts.