Issue Summary

The custom field lists no objects and instead shows “no-options” for unlicensed users on the customer portal when “Filter issue scope (AQL)” has a project name defined.

Steps to Reproduce

1. Create a custom field of type "Assets objects".
2. Now, in the Contexts and Default value > "Assets object/s field configuration" define the project name (Project = ABC) in the Filter issue scope (AQL)

Expected Results

For the customers of Project ABC, the custom field should display all options to choose from in the customer portal for unlicensed users.

Actual Results

For the customers of Project ABC, the custom field shows "no options" for unlicensed users.

Workaround

We can create another "Text" type attribute (maybe Project1) in the schema and copy the project name into this attribute using the value available in the actual "Project" type attribute for Asset objects.

Once this is done, we can then use the text type attribute created earlier in the AQL of the custom field which will fix the problem since they are not restricted in terms of only available for JSM licensed users.