Issue Summary

When adding Assets custom field as Column in Issue Filter View, filtering doesn't show Assets Fields for some JQLs.

This issue only occurs for JQL/filter which returns a large number of work items (benchmarked >~30 issues). As a result, an overall timeout is breached, if Assets Objects being fetched take >~4.6 seconds.

If there are calls being made to Tempeh Service, it is highly likely that this is the root cause. We can see the overall time taken for all batches, and confirm this via logs.

For problems not caused by the timeout issue, check other bug reports such as https://jira.atlassian.com/browse/JSDCLOUD-17817  which has similar symptoms but a separate root cause, which we have already fixed.

Steps to Reproduce

1. Create a Assets Custom field. Create a new ticket with value for the asset field.
2. Do the above for multiple tickets, so that the count of objects increases. This bug is reproducible when there are 1) multiple tickets being filtered, and 2) each ticket has multiple assets custom fields
3. Add Assets Custom field in Issue Filter View as Column. 
4. Add a JQL
5. We see the Assets field shows value as Empty instead of actual values

Expected Results

Assets Field must show the Label (Name) of the field value.

Actual Results

We see the Assets field shows value as Empty instead of actual values

Workaround

We can solve it by limiting the tickets we want to view, using the JQL filter. As of now, this is the only workaround