Issue Summary
When entering keywords in the asset custom field to retrieve related objects in a drop-down list, the focus incorrectly defaults to the keyword entered in the 'Enter Object Key' input field rather than the first object in the drop-down list. This behavior leads to the custom field value failing to update when there is no object corresponding to the entered keyword.
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Navigate to the asset custom field input section.
- Begin typing a keyword to search for related objects.
- Observe the drop-down list that appears with related object suggestions.
Expected Results
The focus should automatically be set to the first object in the drop-down list. If the entered keyword does not match any object, the field should not accept the keyword as a valid entry.
Actual Results
The focus remains on the 'Enter Object Key' input field, displaying the entered keyword. The system expects an object key but incorrectly displays the entered keyword, which does not match any object.As a result, the custom field value fails to update because there is no object with the entered keyword.
Workaround
To manually set the object from the drop-down which needs to be added to customfield.
Bug
Low
072fabfd41a3 as mentioned in the Slack thread you linked, this has been present since 5.13. Can you please update the affected versions please as it affects NBCR. cc 04f71de77d5e