Issue Summary

When using the placeholder ${Issue Type} ( or ${issuetype} )in the Filter Issue Scope of an Assets customfield; if the field is being populated in the Create form, a validation error on the Assets field will block the creation of a ticket.

This does not happen when creating an issue within Jira, or when using other placeholders.

Steps to Reproduce

1. Create an object type and a few objects with Name matches the Issue types used for requests in the portal (e.g. "Change", "Service Request","Hardware")
2. Enable your schema to the JSM portal (see Schema Config>Roles)
3. Configure an Assets CF with the following :
   Filter Scope: objectType = "My OT"
   Filter Issue Scope: Name IN (${Issue Type.name})
   // the same when using ${issuetype.name} )
4. Leave the Filter Assign scope empty
5. Add this field to your request types screen
6. Access the Customer's portal and set Summary, try to select an object in the Assets field - it should only allow selecting an object matching the Issue Type you are on
7. Try to create the ticket in the portal

Expected Results

the ticket will be created, with the selected value in the Assets custom field

Actual Results

 (5.17.n) - the ticket is showing a validation error in the portal: "Please provide a valid value for field 'Assets CF'"

...

Workaround

Only work around at the moment is to remove the placeholder ${Issue Type} from the Filter Issue scope.
For a single value to be selected - try using the Filter Assign Scope, or, a Postfunction to set the Assets field with the same AQL

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: