%*!#&%!380rd Official Hard At Work Thread!%&#!*%
#1001
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1002
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1003
Community Organizer
Thread Starter
The following 2 users liked this post by WhrDLMI:
Roflcopter (12-23-2016),
tacocat (12-23-2016)
#1004
This is why I drink. Seriously...
11/29 - Colleague submits ticket regarding issue with virus scanner preventing software install. Ticket includes the hostname and a whole bunch of other relevant information.
12/15 - Colleague notes that nothing has been done with ticket so he asks me for help/guidance.
12/20 - I send e-mail to a person I believe to be responsible for such an issue asking for guidance.
12/23 - I send a second e-mail because I did not get a response on the first and I am afraid I will forget about this over the holiday. This time I get a response. He can't help but but he knows who can so he CC's that individual.
12/23 - I get an e-mail from said helpful person asking me to submit a ticket with the hostname and IP address of the system having the issue.
This job can be so incredibly frustrating at times.
11/29 - Colleague submits ticket regarding issue with virus scanner preventing software install. Ticket includes the hostname and a whole bunch of other relevant information.
12/15 - Colleague notes that nothing has been done with ticket so he asks me for help/guidance.
12/20 - I send e-mail to a person I believe to be responsible for such an issue asking for guidance.
12/23 - I send a second e-mail because I did not get a response on the first and I am afraid I will forget about this over the holiday. This time I get a response. He can't help but but he knows who can so he CC's that individual.
12/23 - I get an e-mail from said helpful person asking me to submit a ticket with the hostname and IP address of the system having the issue.
This job can be so incredibly frustrating at times.
Lack of accountability/definition of who's job it is to fix this sector. Also, a extreme lack of response time.
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1005
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1006
Community Organizer
Thread Starter
The following 2 users liked this post by WhrDLMI:
Roflcopter (12-23-2016),
tacocat (12-23-2016)
#1007
Community Organizer
Thread Starter
But that is not what I am upset about...
What is making me LIVID is that the guy has the balls to snap back a quick retort saying "you need to submit a ticket" (which is the intuitive over-stressed help desk guy response) without actually reading the GD e-mail! Okay... I put the ticket number in the subject line instead of in the body of the e-mail BUT, if he had read the chain of the e-mail he would have seen where I said to the first guy, "take a look at the ticket noted in the subject."
This is one of those "I've been in your shoes" instances so I can say, from experience, that this dude dropped the ball. Not only did he let this ticket slide for almost a month but he didn't take the time to properly address an inquiry into its status. That is a big part of the job. I don't care how stressed you are, respond in kind. Asshat.
The following users liked this post:
Roflcopter (12-23-2016)
#1008
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1009
IMHO, the problem in this case is lack of accountability. There was a new contract awarded for our help desk and it has created chaos in the extreme. I was told recently that there are some five thousand tickets currently in the backlog. This is also what caused the long response time.
But that is not what I am upset about...
What is making me LIVID is that the guy has the balls to snap back a quick retort saying "you need to submit a ticket" (which is the intuitive over-stressed help desk guy response) without actually reading the GD e-mail! Okay... I put the ticket number in the subject line instead of in the body of the e-mail BUT, if he had read the chain of the e-mail he would have seen where I said to the first guy, "take a look at the ticket noted in the subject."
This is one of those "I've been in your shoes" instances so I can say, from experience, that this dude dropped the ball. Not only did he let this ticket slide for almost a month but he didn't take the time to properly address an inquiry into its status. That is a big part of the job. I don't care how stressed you are, respond in kind. Asshat.
But that is not what I am upset about...
What is making me LIVID is that the guy has the balls to snap back a quick retort saying "you need to submit a ticket" (which is the intuitive over-stressed help desk guy response) without actually reading the GD e-mail! Okay... I put the ticket number in the subject line instead of in the body of the e-mail BUT, if he had read the chain of the e-mail he would have seen where I said to the first guy, "take a look at the ticket noted in the subject."
This is one of those "I've been in your shoes" instances so I can say, from experience, that this dude dropped the ball. Not only did he let this ticket slide for almost a month but he didn't take the time to properly address an inquiry into its status. That is a big part of the job. I don't care how stressed you are, respond in kind. Asshat.
The following 2 users liked this post by tacocat:
Roflcopter (12-23-2016),
WhrDLMI (12-23-2016)
#1010
Community Organizer
Thread Starter
Ah... I've read that some makes do this but I haven't seen it. The only time I have sat on one was a Kia that use the thermoelectric doo-hickey. It was kind of like sitting on an ice pack - it got the job done but not as comfortable as you might think.
The following users liked this post:
Roflcopter (12-23-2016)