Issue Summary

In Jira 5.17 and higher, users with just the customer portal permissions receive error messages when trying to submit request types with Assets custom fields. When trying to do so the user will be able to select from the Asset from the dropdown and it will be filtered properly by the Filter Issue Scope. However upon submission the user will be presented with an error message stating 'Please enter a valid value for field <field name>'.

If the Filter Issue Scope is removed then the issue will submit without an issue. Full Jira users (Agents or Administrators) with rights to the Object Schema can submit issues without the error. Add customers to groups and providing them with explicit permissions to the Object Schema does not resolve the issue either. This issue cannot be replicated in Jira 5.16.0.

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Create a Request Type that has an Assets Custom Field on it.
2. Set up the Assets Custom Field to have AQL within the Filter Issue Scope. I used "Owner like ${reporter.label}" where the owner field is an attribute on the Object. The attribute is of the user type and the portal only user is populated for at least one object in the schema for this attribute.
3. Navigate to the portal and login as the portal only user (no rights to the full Jira interface).
4. Fill out all the required fields including selecting a value for the Assets Custom Field.
5. Attempt to submit the issue and notice the error message.
6. Repeat the same steps with an admin user for example and notice they are able to submit the issue.

Expected Results

User should be able to be a customer and submit issues with Assets Custom fields via the customer portal.

Actual Results

Customer Portal only users are not able to submit issue types that have an Assets Custom Field that contains a Filter Issue Scope.

Workaround

Enabling the assets.aql.scope.filtering.on.issue.update.disabled dark feature will revert the changes made within JSDSERVER-15453 and allow the users to submit the issues through the portal again. However it will remove the changes were added via JSDSERVER-15453.

Note- With this feature flag added, the "Filter Issue scope" configuration on the asset custom field is not respected and you can type and select the Asset Objects from different Object Schema.