Behavior of Filters in the Request App Is Inconsistent

Overview:

When performing filter and search operations in the Requests app (pulling records from mod-circulation/mod-circulation-storage) in Lotus Bugfest, the UI is regularly presenting empty results with record counts greater than zero. A look at the API responses for the queries being performed by the UI show 100 "null" records being returned by /circulation/requests endpoint for the search/filter performed. This does not occur if you also filter by request level. This points to the "ghost" records being old request records from previous Bugfest environments that do not include the "requestLevel" attribute. Some hosting-side clean-up of requests was done to prepare for TLR testing. Could this be related (stale indexes, etc.)?

Steps to Reproduce:

1. Log into Lotus Bugfest as a user with permission to view Requests
2. Click on the Requests app
3. Select a "Request status" filter

Expected Results:

A list of 100 or fewer requests with the specified request status(es) is displayed in the results pane, OR if no results are found the result count is zero.

Actual Results:

No results are displayed but the result count is > 0. If you look at the JSON returned by mod-circulation, there are 100 "null" objects listed.

Additional Information:
URL:
Interested parties: