bleistift2@sopuli.xyz to iiiiiiitttttttttttt@programming.devEnglish · 14 days agoThe state of the ticket systemsopuli.xyzimagemessage-square18fedilinkarrow-up1305arrow-down15
arrow-up1300arrow-down1imageThe state of the ticket systemsopuli.xyzbleistift2@sopuli.xyz to iiiiiiitttttttttttt@programming.devEnglish · 14 days agomessage-square18fedilink
minus-squaremrgoosmoos@lemmy.calinkfedilinkEnglisharrow-up6·13 days agoI hope ticket systems have ways to assign priorities to users, so you can deprioritize any future requests coming from them
minus-squareCevilia (she/they/…)@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up2·13 days agoIt’s been a very long time since I worked on the helldesk but I seem to recall requests were prioritised by a mixture of how critical they are to the business and the seniority of the requester. Past requests had no bearing on future priority. :/
minus-squaremrgoosmoos@lemmy.calinkfedilinkEnglisharrow-up3·13 days agoseniority of the requester. damn. there’s a way to ensure that critical business functions are possibly stalled excessively. hopefully requester priority was just reference
I hope ticket systems have ways to assign priorities to users, so you can deprioritize any future requests coming from them
It’s been a very long time since I worked on the helldesk but I seem to recall requests were prioritised by a mixture of how critical they are to the business and the seniority of the requester. Past requests had no bearing on future priority. :/
seniority of the requester. damn. there’s a way to ensure that critical business functions are possibly stalled excessively.
hopefully requester priority was just reference