"Unassigned Tickets" alert for assigned tickets.

matthewmarch · 2017-10-25T07:03:29.000Z

We’ve just a re-import of our tickets and closed/open tickets have active alerts claiming to be unassigned, when they’re not.

Anyone else come across this and know how to fix?

uzairsaqib · 2017-10-25T08:39:01.000Z

I am not much aware about Spiceworks functionality behavior but being an Oracle Programmer I think by importing the data into tables some trigger (event) has been fired in which the boolean state of all imported ticket have been changed into un-assigned. You have to check at back-end in table where tickets are being stored and I believe you would easily find the difference between an assigned ticket and un-assigned ticket. There from you can upate all those tickets from unassigned to closed or assigned as required.

But, I am repeating that I am not sure about Spiceworks behavior, and I concluded above just based on a scenario and expected behavior of Spiceworks. It is better to wait to get solution from an expert of Spiceworks.

matthewmarch · 2017-10-25T08:53:54.000Z

Makes sense. I’ll give that a go.

Thanks for the suggestion!