Issue Summary

A custom field has a field context which includes the following filter scope AQL:

objectType = "Groups" AND "PrimaryEmailAddress" like "<customer>.com" AND Status = ACTIVE 

Using an advanced filter in the Assets UI with this query results in 54k results returned.

Within the custom field configuration / Field context / Assets, the Allow search filtering by these attributes includes Name, PrimaryEmailAddress, ManagedBy.

Name and PrimaryEmailAddress are of type Text and ManagedBy is of type User.

When selecting the drop-down field on the portal related to the field context referenced above, entries are returned (first 50, I believe).  However, if you attempt to type a value to filter the list by one of the attributes mentioned, it fails for ManagedBy.

There is no error that displays, it just doesn't find any results

Steps to Reproduce

1. Using a system with a large data set where one of the objects in the dataset is of type User
2. Create an Assets custom field with a work item filter scope similar to the one referenced in the description
3. Include in the filtering by these attributes (in the field context) an attribute that is of type User
4. Include this field on request type
5. On the portal, using the request type in step 4, attempt to filter the results displayed by the attribute that is of type user

Expected Results

The user should be able to filter the list down to the specific user they type in

Actual Results

The following can be seen in chrome/network tab

"reasonKey": "cmdb.generic.error"

"reasonCode": "500" 

The following exception (partial) was noted as well.

msg: Read timed out
     stack: java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
	....

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available