Issue Summary

When using filter issue scope to filter Insight/Assets objects using the reporter placeholder (for example ${reporter.id}), Insight objects can be found and selected correctly in Jira and on the Customer Portal. However, when trying to submit a request on the Portal, a validation error occurs – "Validation failed for Insight object".

Steps to Reproduce

1. Create an Insight/Assets object type (for example Users) with a user attribute named "User" and set it to reference Jira users.
2. Create a JSM project and ensure there is a customer or user whose Jira account is linked in the Users object type (i.e. their "User" attribute points to that account).
3. Create an Insight/Assets custom field and set the filter issue scope to use the reporter placeholder, for example: "User" = ${reporter.id}
   (or as part of a more complex AQL, e.g. using HAVING with other object types).
4. Add the Insight/Assets custom field to a request type in the JSM project so that it’s visible on the Customer Portal.
5. As the affected user (whose account is linked in the Insight object), go to the Customer Portal > open the request creation screen > search for and select the Insight object linked to that user.
6. Notice that search results are correctly filtered and the object can be selected.

Expected Results

The request is successfully submitted, and the selected Insight/Assets object is stored in the custom field.

Actual Results

The request fails to submit with the validation error shown on the Insight/Assets field:

Validation failed for Insight object

This occurs even though:

The reporter has a matching object where "User" is populated with their Jira account, and

The same AQL, when tested with the reporter’s accountId hard‑coded, returns results.

Workaround

Change the AQL to use the Assets function currentReporter() instead of the Jira placeholder ${reporter.id}. For example:

Before (problematic)
"User" = ${reporter.id}

After (works as expected)
"User" = currentReporter()