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.

  • aelwero@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    2
    ·
    1 year ago

    Embellishing the priority of a ticket isn’t being fair and is an attempt to alter the order of requests… gotta play by the rules if you want the rules to be upheld.

    • deweydecibel@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      8
      ·
      1 year ago

      You don’t have to give them priority for playing up the urgency, but they suggested actively pushing the ticket to the back out of spite and avoiding the ticket when they have nothing else to do.

      Which is fucking childish. Do your damn job.

      • Echo Dot@feddit.uk
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        It really does depend on how often they do it though. If it’s once or twice then I don’t really care, but if they do it all the flipping time then they need to learn.

        It’s actually inefficient from a time keeping point for them to continuously do that and for me to continuously have to alter ticket statuses back for tickets that are actively in progress, but are waiting for an engineer or a part to become available.

        Them changing the status every 5 minutes actually makes more work for me and doesn’t speed the ticket up at all.