Issue Summary

When adding Assets custom field as Column in Queue and the JQL has status column to filter then Assets field shows as None. 

This issue only occurs for customers who have migrated before Assets was onboarded to DataPortability, and the root cause of this bug is that there are >1 unique Workspace IDs related to Assets objects. This will be the case for all S2C and C2C migrations done before Assets was onboarded.

If there are calls being made to Assets Service, it is highly unlikely that this is not the root cause.

For problems not caused by >1 unique Workspace IDs, check other bug reports such as https://jira.atlassian.com/browse/JSDCLOUD-18172 which has similar symptoms but a separate root cause we are working on a resolution for.

Steps to Reproduce

1. Create a Assets Custom field > Create a new ticket with value for the asset field.
2. Add Assets Custom field in Queue as Column.
3. Add a JQL with status filter status = Open.
4. We see the Assets field shows value as NONE instead of the label value.

Expected Results

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

Actual Results

Assets Field value shows as NONE

Workaround

Remove the Status filter in JQL and it works in few cases.