I’ll add one more thing:
I had hoped the answer would be to turn on “Require Assets to be Confirmed” in the Site Options:

But then I realized folks can just straight up choose to ignore it lol

So that doesn’t really solve anything.

@zige Thank you for submitting your question to our community! This is one instance than many other districts have found themselves in. One way that @EStapf_iiQ found to require an asset tag on a Quick Ticket would be to add a required custom field to enter the asset tag before they can submit the ticket: 

We have this issue as well in our district.  After much thought and frustration, I added two custom fields to the ticket.  

1.  Assigned Owner 
2. Assigned Device

I made both fields required for select ticket categories and campuses.  I then sent out a training video how to submit tickets correctly.  I also added if the campus then completes the tickets correctly I would remove the required fields from their campus.  We still have several campuses that do not always enter the ticket correctly so they are still required. 

After the ticket is submitted they see the following confirmation message to remind them of the information needed in the ticket.  The tickets are all reviewed by our Help Desk team and they will link the assets in the ticket with the required field information.  Our technicians then verify the device when it is picked up and submitted for repair.  

Thank you for the suggestions @ashort and @Kathryn Carter.

Using a custom field to require the asset number be added to the ticket is helpful, so at least its in there somewhere.

With that said, this doesn’t actually link the ticket to the asset without someone going in and adding it after the ticket has already been submitted, like you described, @ashort.

This will likely need to be added as an enhancement request.

For our district, we’ve been struggling with this issue as well. Our work around was focused on training the techs to link the asset before closing the ticket instead of trying to train all our staff on how to put in the tickets correctly.

We have a set rule in place that adds a tag to the ticket if it’s linked to a general model category and not a specific asset. Then once a week our department head looks at the list of tagged tickets and just has the techs correct them as needed. Right now its just for chromebooks in our district, but hopefully once we manage our inventory a little better we can expand it out more.

This unfortuntely does not answer your question and is only a work around until incident IQ adds this as a feature. I’d love to see something where you have to link an asset or a ticket has to be resolved with asset linked kinda deal. It still has its issues (IE, someone links the wrong asset it doesnt get caught in the tags), but it has helped us a alot. I’ll attach an image of the rule below incase anyone wants to see.

 

@DPetroski 300251b milforded Thanks for adding your workaround to this thread! I love the idea of using that rule to add the tag. While it might be a manual process at the moment for updating the tickets, it is a good workaround.