Allowing the usage of asset association like is done for incidents would be very helpful. All tickets no matter the designation should have that ability.
I’ve got to believe this is an oversight as I cannot fathom a reason why this isn’t allowed already in service catalogs if attachments can be associated by options designated. Having to now use the asset dataset in a dropdown that doesn’t associate the asset, only let’s you search on name of asset and encompasses all assets is clunky to say the least. The best option is already there for incidents and just needs a little tweak.
Good reasons:
-Incidents allow the asset association automatically
-Incidents allow this to be auto filtered on your own assets or in “other assets” as “in use” by, location, product, etc if performing for others
-Align all ticket types with the same familiar options no matter the interface being used
-Auto associates assets chosen to the ticket
-Onboarding/offboarding would work so much better as they are built off of service catalogs and not incidents. Allowing requesters to easily pick items in locations or for the “requested for” entities
