Issue Summary

When a Jira issue is created with asset custom fields, attempting to move that issue to a different project or issue type result in the error message: "Could not find Assets object/s."

Steps to Reproduce

1. Begin by creating an asset schema along with two distinct object types.
2. The first object type is named as "Replication," while the second is named as "User."
3. Within the "Replication" object type, create an attribute called "Issue type." The type will be set to default, and the type value will be text.
4. For the "User" object type, configure a new attribute named "reference," which will be of type object, linking it to the first object type, "Replication."
5. Additionally, set up another attribute called "user" with the type set to user. This configuration will allow the "Replication" object type to have an inbound reference from the "User" object type.
6. Create several objects within both object types.
7. Create an asset custom field named "ACF."
8. Configure the filter scope to include objectType = Replication.
9. Set up the Filter Issue Scope (AQL) with the condition - "Issue type" = ${issuetype.name} and object having inR(objectType = User and User = currentUser())
10. Create a new project and associate the custom field "ACF" with this project, ensuring the issue type matches the value specified in the "Issue type" attribute.
11. Create an issue by populating the asset custom field, "ACF."
12. After the issue is created, attempt to move it to the new project; this action will fail and display an error.

Expected Results

The expected result is that moving Jira issues to other projects should be successful and should not throw errors.

Actual Results

Moving Jira issues to other projects fail with error could not find Assets object/s.

Workaround

The issue is not reproducible after removing the Filter Issue Scope (AQL) ie  "Issue type" = ${issuetype.name} and object having inR(objectType = User and User = currentUser())