Make Filters Persistent
I constantly have to keep changing filters on the Helpdesk to filter out closed and resolved tickets. By default you should only be looking at tickets that are currently open. I have no clue why this system defaults to all tickets.Please at least make filters persistent/sticky, so that once I have filtered the dashboard the way I want to view it, it stays that way. Constantly have to reapply filters throughout the day so that closed and resolved tickets are not cluttering up the view of current tickets we're trying to work on is a must!
Last Modified Date For Helpdesk Queue
When looking at open tickets, we need to be able to sort the tickets by last modified date. I currently have no way to quickly determine what tickets have been sitting idle in the queue. This would also help to put tickets at the top of the queue that customers have recently replied back on. Knowing when a ticket was last updated is a must have.
Re-Arrange Categories
The ability to re-arrange our categories by either drag and drop or even an up and down arrow would be a great addition. Currently, the only way to re-arrange the ticket categories is by renaming them (which then changes all the tickets that category is associated with) or deleting all of the ones below where you want to put the new one in the list. It makes it very tedious to keep the categories in alphabetical order for ease of use for our end users.Helpdesk - Ticket Last Updated and Last Updated By fields
In GoToAssist we could see who last updated a ticket and when. We could sort by "Last Updated" and also see a field "Last Updated By" to see when a ticket had had some activity by a customer or technician. This enabled us to easily see on the ticketing screen when a customer had responded with more information or was OK for us to close the ticket. Can we please have this feature as a matter of top priority as we are not able to respond in a timely manner to our customer queries. Thank you.Ti
WorkFlows
I would like to suggest the addition of workflows or approval flows for tickets. User requests a new device. Request goes to Manager. Manager can then approve or deny a request. Leaving notes for each response. Approval sends ticket to IT for fulfillment. Deny sends ticket back to user as closed with explanation. (Explanation required for deny.)
