Issue Summary

When looking up users for display in Assets custom fields, some users will not included in the list. This appears to be because Assets is not treating "JIRAUSERXXXXXXX" user keys correctly.

Steps to Reproduce

1. Create two users in the system
2. Using the database table "app_user" update one of them to have their "user_key" to match their user name
3. Create a test schema and create an objectType called "Employees"
4. Add a JiraUser attribute to the "Employees" objectType
5. Create two new Assets Employee objects to match the two Jira users and set the JiraUser attribute to the Jira user for each one
6. Create a user picker custom field and apply the context to the project and appropriate screens
7. Create an Assets custom field with the below settings:
   • Object Schema: <The created schema>
   • Filter Scope: objectType = Employees
   • Filter Issue Scope: Name = ${<user_custom_field_name>.name}
   • Filter Assign Scope: Name = ${<user_custom_field_name>.name}
8. Create a new ticket in the project in question. In the new issue screen set the user picker field to the user who has the userkey which matches the username in the database
9. Observe that the user list in the Assets field will find the user.
10. Now, in the same new issue screen set the user picker field to the user who has the userkey which does not match the username in the database

Expected Results

The appropriate user(s) will show up.

Actual Results

Only users which have the user key and username matching are displayed. Which, in this case, the user will not show up.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.