Once had a user manually change their ticket to Priority 1, which we used to indicate dozens of people/everyone down, because their M key only worked half the time they pressed it.
Once had a user manually change their ticket to Priority 1, which we used to indicate dozens of people/everyone down, because their M key only worked half the time they pressed it.
Every ticketing system that I’ve used actually does have this! The service desk finagles it to get the desired “priority” that will make the end-user happy. We have the option to correct it once it gets to us.
I think that’s because many ticket systems implement the ITIL priority matrix??, or something. I’ve been away from helpdesk for a number of years now and only kind of rember a matrix I probably only kind of correctly described.
Our system let users pick only some of the matrix values, they couldn’t declare a high priority, high impact, high urgency, ticket on their own. Like you, we handled setting the “true” value once the ticket was moved past level 1/evaluated by someone in IT.
Yup, we use a decently popular ticketing system that follows this, even has a mini training course to allow you to understand it all iirc
I think you are exactly correct on that! It is something that seems like it would be useful, but nowhere I’ve ever worked used it correctly.