Custom field searcher for assets no longer displays as a dropdown menu

Question

Good afternoon,

After the UI change our setup to quickly log a ticket has changed.  We use the create button at the top of the screen in JSM > custom request types that function as templates.

Any of our custom fields that sit in our request types no longer display as a dropdown menu, unless we click on + Add object.

The custom field points to an asset database, it seems to do this with every custom field that searches for assets.

Max Fialkow · Answer

Hello team. This is a confusing change for everyone. 
It also stopped showing the total count of options, which was really useful.

Sascha Harms · Answer

Hi Marc,

Thank you for your reply and welcome.

Nothing has changed from our end.

Does it still work if you go to the portal and make a request?

Yes it shows up as a dropdown.

Abubakar Pokam Tchawa · Answer

We recently had this at work. It seems that this is now the default way Atlassian displays Assets fields when you try to create them from the Agent view.

However, on the portal, Asset fields without any dependencies will still be displayed as dropdowns. If an Asset field has a dependency (i.e., a Filter Scope that depends on another field), it will be displayed this way as well.