Senior IT engineer enters the room and quietly talks to a coworker about a job related issue.

Another coworker decided to troll the sysadmin.

CW: *yells* "Open a ticket!" (That's the sysadmin's regular reply)
IT: *ignores*
CW: *trying to get his attention* "Open a ticket first! Then come back"
IT: *gives him the stare of death*
CW: "Go away and open a ticket!"
IT: *silently leaves the room*

After no more than a minute CW gets a reject from all networks outside the company's VPN.

IT comes back into the room, get's intimately close to CW's ear and says "Now open a ticket".

👋

🎤

Manager: We need to setup the security in the Mexico server

Dev: You mean that 3rd party firewall add on?

Manager: Yes

Dev: And set up the billing on the Mexico account?

Manager: Yes

Dev: lol, sure thing I’ll create the ticket

Manager: What’s so funny?

Dev: Nothing

Ticket: Build wall and get Mexico to pay for it.

First day at work:
To install IDE - raise a ticket.
To get access to source control - raise a ticket.
To get access to bug tracker - raise a ticket.
To raise a ticket, I need first to connect to the intranet, but to do that, I need to raise a ticket.
AND even before that, I need a username to login to my laptop, raising a ticket is also required.
WTF?!!!

A group of programmers and marketers were traveling to a trade show on a train. Each of the marketers had bought a ticket, but the programmers had only bought one ticket for the lot of them.

One of the programmers was keeping a lookout, and when the conductor neared their car he called out "The conductor's coming!" and all of the programmers piled into the train's lavatory and closed the door. The conductor took the tickets of all of the marketers, and then knocked on the lavatory door and called "Ticket please." The programmers slid their ticket under the door, and the conductor took it and left.

The programmers were laughing at the marketers for the rest of the trip, and the marketers felt like idiots.

On the way back, the marketers decided they would use the same trick and only bought one ticket for them. But this time, the programmers didn't buy a single ticket! Again, one of the programmers kept a lookout for the conductor. When he called "Conductor coming!" all of the programmers piled into one lavatory, and all of the marketers shut themselves into another lavatory.

One programmer came back out of his lavatory, knocked on the other door, and said "Ticket please!"

I prefer silent kills.

× open Jira ticket classified as a BUG REPORT
× Title: "Mike"
× Description: "Mike is working with us"
× assign it to Mike

× reopen it every time it's closed

"Opps.. I'm sorry, but you have insufficient rights to open this Ticket."

Well. You know what? I AM THE FUCKING SYSTEM ADMINISTRATOR YOU CUNT!
YOU HAVE INSUFFICIENT RIGHTS to restrict me access to that fucking ticket!

"Oh. In that case, go ahead."

THANK YOU. FUCKING PRICK.

‪How to get your Jira ticket resolved:‬

‪1: Assign in it the person‬
‪2: Mention him on the ticket‬
‪3: Remember the ticket number ‬
‪4: Sneak into his office‬
‪5: ‬

How not to give support..

Me: Creates ticket on support site, letting them know their webservice returns "maintenance" page.
Support: "It works on our end."
Support: *closes ticket*

Euhm.. excuse me?

Me: Creates another ticket with a screenshot and the curl response information..
Support: Sends screenshot back that it works on their end. "Maybe check your firewall"
Support: *closes ticket*

I ain't playing these games..

Me: Creates new ticket with more curl responses from 4 different servers to prove it's not "firewall" related.
Support: ..

2 days later

Me: Sends *friendly* reminder.
Support: ..

6 days later

Me: Creates ticket again saying I'm still having issues.
Support: "I'm forwarding this to our technical support"
Support: *closes ticket*

10 minutes later.

Technical Support: "Here's the manual for our integration .pdf."

Excuse me, you say what now? I KNOW HOW IT WORKS, I'VE WRITTEN THE INTEGRATION ALREADY. THE SERVICE JUST SEEMS TO BE DOWN FFS.. pls..

Me: Sends mail to their project manager who manages the clients dossier with support history and such.
Him: "I'll check it out and let you know."

1 day later.

Support: "We had some issues this and that, wasn't publically availble, works now, .."

What a nice way to waste your time..

Wife : Lets try some other position tonight.

IT support guy : raise a ticket for change request

COVID-19
Why it sounds like a JIRA ticket?

There's one kind of ticket I fucking love. Wait, YOU LOVE TICKETS?! No, except for one.

Tickets where people ask us to restore backups.

Why do I love them?

Because the only fucking thing I need to do is reply with a link to a helpdesk item on our website because backups aren't something within our support range because it's easy for customers to do.

So whenever a ticket about restoring a backup comes in, it's as easy as opening the ticket, pasting the link with "I'd like to refer you to the following resource: " and pressing fucking "reply"

😄

Mon: Ticket A is now low priority, Ticket B is top priority

Tues: Ticket B is now low priority, Ticket C is top priority

Wed: Ticket C is now low priority, Ticket D is top priority

Thurs: Ticket D is now low priority, Ticket E is top priority

Manager (Fri): You haven’t completed a ticket all week! What gives??

Manager (Following Mon): Tickets A, B, C, D AND E ARE TOP PRIORITY!!!!!

Dev: …

Any idea why normal, intelligent people lose the ability to write coherent sentences as soon as they click into a bug ticket description text box?

Hey, Root? How do you test your slow query ticket, again? I didn't bother reading the giant green "Testing notes:" box on the ticket. Yeah, could you explain it while I don't bother to listen and talk over you? Thanks.

And later:
Hey Root. I'm the DBA. Could you explain exactly what you're doing in this ticket, because i can't understand it. What are these new columns? Where is the new query? What are you doing? And why? Oh, the ticket? Yeah, I didn't bother to read it. There was too much text filled with things like implementation details, query optimization findings, overall benchmarking results, the purpose of the new columns, and i just couldn't care enough to read any of that. Yeah, I also don't know how to find the query it's running now. Yep, have complete access to the console and DB and query log. Still can't figure it out.

And later:

Hey Root. We pulled your urgent fix ticket from the release. You know, the one that SysOps and Data and even execs have been demanding? The one you finished three months ago? Yep, the problem is still taking down production every week or so, but we just can't verify that your fix is good enough. Even though the changes are pretty minimal, you've said it's 8x faster, and provided benchmark findings, we just ... don't know how to get the query it's running out of the code. or how check the query logs to find it. So. we just don't know if it's good enough.

Also, we goofed up when deploying and the testing database is gone, so now we can't test it since there are no records. Nevermind that you provided snippets to remedy exactly scenario in the ticket description you wrote three months ago.

And later:

Hey Root: Why did you take so long on this ticket? It has sat for so long now that someone else filed a ticket for it, with investigation findings. You know it's bringing down production, and it's kind of urgent. Maybe you should have prioritized it more, or written up better notes. You really need to communicate better. This is why we can't trust you to get things out.

*twitchy smile*

Dear clients.

Putting your support subject or content either in uppercase letters or telling US that your matter/ticket has 'the utmost priority' doesn't mean anything to us. You'll just have to keep in line.

WE decide the priorities. Also, calling us when we haven't looked into your very fucking high priority ticket yet for about 5 FUCKING minutes is NOT going to help YOU.

- One of the Linux Support Engineers.

Just got this little stinker added to my board this morning….

Ticket Title: Weird shit going on in app

Ticket Description: (blank)

Attachment: <Screenshot of app logo>

Manager: Well what do you think is causing it?

Dev: Causing what?? This ticket doesn’t describe anything at all

Manager: Well it’s a bunch of different things! The ticket is just a high level summary. Now how long do you think it’ll take to fix?

Dev: …

Product: Hey, this screwdriver feature I never requested isn’t there. Why? Can you fix it? It’s kinda urgent.

Product: @Root please jump on the ticket above … fairly urgent.

Root: It’s Friday, I’m out next week, and I’m working on finishing <urgent comma ticket> right now.

Boss: Work on the screwdriver instead. But make sure you finish the comma ticket too!

Boss: By the way, I volunteered you for eight security reviews next month!

Security: You’re on call for AWS audits next month, too!

Client hasn’t responded to my questions for over 2 weeks, so I close her ticket.

”Why the hell did you close the ticket!? The problem still exists!”

Sorry, I’m not a mind reader..

Being a student this was how my colleagues felt about my code and SQL procedures. They didn’t even let me create a change ticket to present to CAB 😂

Had QA call my "simple, quick" ticket a "monster ticket" in front of everyone. Hear it and weep, micromanager!

Also had them tell me i thought of everything, it was beautiful, and that i have a knack for frontend :)

Every week is the same. Wake up, new jira ticket. “Build us a pink house”.

*i build a house*

Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT”, click on ticket, “bug report: the house doesn’t have sprinklers”

They didn’t ask for sprinklers. This is not a bug. *i add sprinklers*

Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT ASAP ASAP ASAP”, click on ticket, “bug report: the house is pink.”

HOW IS THAT A BUG TWO DAYS AGO IT WAS LITERALLY A REQUIREMENT

Meanwhile management makes triple my salary

Team Lead: don't ask me to help with your problem, open a ticket
*opens ticket*
*ticket gets routed to team lead*

Hahahaha :D

*In teams meeting with client*

Manager: Yes we can do all of that and it will be actioned very quickly. We will make all of these feature requests top priority. We will set aside everything we are currently working on in order to get this done!

Dev: ...Are you writing any of this down?

Manager: I don't need to, I always remember everything!

Dev: Just so you are aware, I'm not writing anything down. You're going to need to create a ticket with requirements spelled out for each one of these promises you're making otherwise they won't get actioned by the team.

Manager: I know that!

Dev: ...

*Later that day*

Ticket Title: Action client feature requests TOP PRIORITY!!!

Ticket Description: *empty*

Dev: ...

Them: Root, you take too long to get tickets out. You only have a few simple ones. You really need to rebuild your reputation.

Also them: Hey, could you revisit this ticket? Could you help ____ with this other ticket? Hey Root, how do you do this? Root, someone had a suggestion on one of your tickets; could you implement that by EoD? Hey Root, i didn't read your ticket notes; how do you test it? Hey, could you revisit this ticket for the fourth time and remove some whitespace? Hey Root, someone has non-blocking code review comments you need to address before we can release the ticket. Hey Root, we want to expand that ticket scope by 5-6 times; still labeled a trivial feature though.

Also them: Super easy ticket for you. Make sure you talk with teams A, B, C, D, E and get their input on the ticket, talk with ____ and ____ and ____ about it, find a solution that makes them all happy and solves the problem too, then be sure to demo it with everyone afterward. Super easy; shouldn't take you more than a couple days. Oh, and half of them are on vacation.

Also them: Hey, that high-priority ticket you finished months ago that we ignored? Yeah, you need to rewrite it by tomorrow. Also, you need to demo it with our guy in India, who's also on vacation. Yes, tomorrow is the last day. (The next day:) You rewrote it, but weren't able to schedule the demo? Now you've missed the release! It's even later! This reflects very poorly on you.

Also them: Perfect is the enemy of good; be more like the seniors who release partially-broken code quickly.

Also them: Here's an non-trivial extreme edgecase you might not have covered. Oh, it would have taken too much time and that's why you didn't do it? Jeez, how can you release such incomplete code?

Also them: Yeah, that ticket sat in code review for five months because we didn't know it was high-priority, despite you telling us. It's still kinda your fault, though.

Also them: You need to analyze traffic data to find patterns and figure out why this problem is happening. I know you pushed the fix for it 8 months ago, and I said it was really solid, but the code is too complex so I won't release it. Yeah I know it's just a debounce with status polling and retrying. Too complex for me to understand. Figure out what the problem is, see if another company has this same problem, and how they fixed it.

-------------

Yep. I'm so terrible for not getting these tickets out, like wow. Worst dev ever. Much shame.

LF work, PST.

I literally just got a ticket that says "make the scrolling easier"

gonna be a great fucking day

Hey @Root! I know you won't have time to finish Ticket A before holiday vacation, so work on Ticket B instead.

I finished Ticket A in time. except for converting/fixing some horrible spaghetti monstrosity. More or less: "we overwrote this gem's middleware and now it calls back into our codebase under specific circumstances, and then calls the gem again, which calls the middleware again." Wtf? It's an atrocity against rationality.

The second day after vacation:

Hey @Root, drop Ticket B and work on Ticket C instead. Can you knock this out quick, like before friday? ... Uh, sure. It looks easy.

Ticket C was not easy. Ticket C was a frontend CSS job to add a print button, and for unknown reasons, none of the styles apply during printing. The only code involved is adding a button with a single line of javascript: `window.print()`, so why give it to the chick who hasn't been given a frontend ticket in over a year? Why not give it to the frontend guy who does this all day every day? Because "do it anyway," that's why.

And in somewhere between 13 (now 5) minutes and two hours from now, I'm going to have a 1:1 with my boss to discuss the week. Having finished almost all of Ticket A won't matter because it's not a "recent priority" -- despite it being a priority before, and a lot of work. I've made no progress on Ticket B due to interruptions (and a total and complete lack of caring because I'm burned out and quite literally can no longer care), and no progress on ticket C because... it's all horribly broken and therefore not quick. I assigned it to Mr. Frontend, which I'll probably get chewed out for.

So, my 1:1 with bossmang today is going to be awful. And the worst part of all: I'm out of rum! Which means sobriety in the face of adversity! :<

but like, wtf. Just give me a ticket and let me work on it until it's done. Stop changing the damn priorities every other freaking day!

> Manager gives me new ticket.

> This seems like a ticket Dingus would do.

> Remember Dingus got fired a month ago.

> Realize I’m the new Dingus.

!!rant
!!ANGER

Micromanager: "Hey, Root!

Since you're back, and still not feeling well, we have an easy ticket for you: Rewrite the slack integration gem! Oh, you don't have to re-implement all of it, just make sure it all works the same way it does now. That bitch you worked with once over a year ago who kept throwing you under the bus to management and stealing credit for your work? Yeah, she wrote the original code like four years ago. It's perfect, so don't touch it. but she can fill you in on all the details you need and get you up to speed on how to test it.

But yep! It should be simple. and I just knew you would love this ticket, so I saved it just for you. Nice and quick, too, to get you an easy win.

You know, since you have to repair your reputation with product. and management. and the execs. and the rest of the team. and me. Yeah, product doesn't trust you so they don't want to give you any tickets. They just can't trust you to get them out and have them work. So you have a lot of hard work to do."

Spoiler: The bus-thrower wasn't much help. (Surprise.)
Spoiler: The ticket was already in my backlog -- one of a grand total of two tickets.
Spoiler: I don't find the ticket fun. Maybe if I was to write the entire implementation with a nice DSL? but no, "don't touch the perfect code." Fuck you.
Spoiler: It isn't going to be nice or quick. But, she (micromanager) is looking to lose me, so that really is an easy win. for her.

And. just. argh. fuck you. i've been exhausted and dying for well over a year, but you've kept ignoring that (and still are, despite me providing goddamn legal forms from fucking doctors stating it in plain fucking english, which you also fucking ignore), and you just keep piling on the work and demanding the ridiculous of me despite it. Yeah I can pull it off sometimes. No, I really shouldn't, and I'm surprised I can. (also, "Time off? What, and lower your productivity even more? ____ doesn't even take vacations. And how are you doing on that ticket?") And no, none of my tickets have ever had any fucking problems. Not even when there are upstream service outages. Not. a. single. fucking. one. Ever. And the only things I've ever missed were things that bloody product never put in the fucking ticket, so fuck you with your "repair your reputation" bullshit.

god, i fuckiNG HATE THESESTUPOID ANWETLJAF SAJEWTKW BITCHFACEDUCKFUCKERS

Why the FUCK am I still fucking working here?
Right, because I've been burned out and dying so much I can't pass a fucking interview so I can fucking leave.

jasdkl;fk

ugh. Anyway. If you ever find yourself starting work at a Cali fintech company whose internal mascot is a very fine duck? Just run. I absolutely guarantee you will be miserable.

-Can I get a ticket please?
-Return?
-Naah.

Dev: To send push notifications, please open a ticket to get access to the new tool we are using which is dedicated to managing push notifications and push notification campaigns.

Me: ok done.

*5 days later*

Tool owner: Can you please add to the ticket the reason you need access?

Me: “To use it”

Start working on ticket
Looks at code
WTF is the shit?
Open devRant to rant
1.5 hours later
what was I doing?

Hey Root. Here’s a new ticket for you. It involves lots of things you’ve never seen before, and the only person you can ask is out this week.

Hey Root. Why haven’t you been making good progress every day? Why didn’t you reach out to the guy on FTO? Clearly you can’t communicate. Give me detailed status updates twice a day at specific times, covering <exhaustive list of topics> so I know you’re working. What do you mean “no”!?

Hey Root. Stop working on that ticket, and work on this other ticket. It’s the same thing, but different. High-priority!

Hey Root. You asking questions about that ticket pissed off a legendary golden boy principal dev, and he said it’s a bad idea and that we should have assigned it to a different team, too — you know, the team who usually works on these areas. But we might still have you do it. Please work on the previous ticket that’s in the exact same area until we decide.

Hey Root. Why haven’t you gotten anything done?

I wrote an app that tells me if a lottery ticket is winning. It takes a picture of the ticket, does OCR, finds the number lines and compares them with a remote json.
I live next door to a lottery shop.

Manager: I NEVER SAID THAT!!

Dev: *Brings up email where he said exactly that*

Manager: I DON’T REMEMBER ASSIGNING YOU A TICKET TO LOOK THAT UP. GET BACK TO WORK!!

Dev: …

A friendly reminder that Deutsche Bahn fucking sucks.

Their trains show up 10 minutes later than they would have to everyday.

Once I saw that there was a train that was 120+ minutes late.

Today I had to wait almost 20 minutes at a SINGLE train station. Thus I couldn't enter the next train.

To my luck the next train arrives in an hour.

EDIT:

As a student it makes my life way harder than it already is.

It is not reliable at all.

They charge you with 60€ if you forget your ticket btw.

I don't forget my ticket though. My ticket is my campus card.

Their tickets are fucking overpriced and they are always damn late. I ain't paying for that shit. I would rather ride with a horse to the university than paying for a ticket.

Second EDIT as an update:

They just announced that my next train is going to come 10 minutes later. What a bloody surprise, eh?

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---

> Customer logs Jira ticket claiming app is not working
< I restart the app, investigate and explain tht their server has issues
ø Client closes the ticket as Resolved
-- a couple of days pass by ---
<...>

< I log a JIRA ticket explaining what and how is wrong with the server with suggestions how to fix the problem so the app will not crash any longer (client own the server, has his own sysadmins -- I don't even had permissions to open syslog.. had to hack dmesg on their PROD server to pin-point the issue)
> no reaction from customer for weeks. I ping the ticket

× app crashes again

> no reaction from customer for weeks. I ping the ticket
> customer leaves a comment that their sysadmins are looking at it trying to figure out what might be wrong (ignoring what I wrote in ticket's description??? srsly?)

× app crashes again
< I post detail investigation details: snips from logs, screenshots, everything with crystal clear explanations.

> no reaction for weeks
......

well that's fun..

Dev: Your PR only addresses a quarter of the ticket

Dev2: *limps a commit so that now 1/2 of the ticket is addressed and creates a new PR for a separate ticket*

Dev: Your original PR only addresses half of the ticket

Dev2: *limps a commit so that now 3/4 of the ticket is addressed and creates a new PR for ANOTHER new ticket*

Dev: Your original PR only addresses 3/4 of the ticket

Dev2: *limps a commit so that now all of the ticket is addressed but two new bugs are introduced and creates a new PR for ANOTHER new ticket*

Dev: Your original PR introduces 2 new bugs

Dev2: *limps a commit addressing one of the two new bugs and creates a new PR for ANOTHER new ticket*

Dev: Your original PR still has one bu—

Manager: WOW GOOD JOB DEV2 THAT’S 5 PRs TODAY AMAZING! Dev you need to pickup the pace, you only have 2 PRs so far today. And get these PRs from Dev2 QA’d fast. He’s a rockstar!

Dev: …

*The 4 other PRs turned out to be equally dogshit*

Manager: Hey hurry up with QA, you’re holding Dev2 back!

Dev: …

Manager: I just created a new ticket! The website flashes when you reload it!

Dev: Yes, that's typically what happens when you reload a website.

Manager: ...

Dev: ...

$work: Ey @Root, make this super simple thing.
$work: No, not like that.
$work: It also needs to do A, B, and C.
$work: No, not there. You should build it somewhere else, but I won't tell you where.
$work: You need to build out F and G, too.
$work: What do you mean you don't have the data? Just ask support drone #3. (who directs me to #2, and that one to #8 who doesn't know, and that one to #12 who won't answer)
$work: Why can't I do K, Y, or S? You should be able to infer these from the mind of whoever wrote the ticket by its wording, despite no mention of them whatsoever.
$work: Are you done yet? It's a super simple ask!

That damn moment when you find out ... that ticket you spend a lot of time doing, well, there is a library for that.

The submit button is the wrong color orange.
Priority:BLOCKER

This is no meme, this is an actual customer support ticket we got :)

when the project manger asks for status on a ticket.
me: what ticket
pm: hold on. (makes ticket). that one.

Internal support article to get access to a tool:

"To get access click 'NO' in the 'was this article helpful section' and open a support ticket, making sure to mention the tool you are looking to get access to"

What fucking fresh hell is this? Why not have the article, contain the fucking link to open the ticket.

You have intentionally put up a useless article, in order to hack your way around this stupid system.

Worst part of being a dev:

Writing down an issue in the ticket system for somebody else took longer then fixing the issue yourself.

I think this ticket machine will definitely benefit of a hardware upgrade

Ah... The satisfying feeling when you close a ticket with Not an Issue aka the User is Dumb...

Though it took a long time to get the evidence I needed...

Jira ticket

Intranet not working.
Delete certificates.
Still not working.
Ask IT.
You need to create ticket to delete certificates.
IT site is in intranet.
Intranet not working.
Ask IT to create ticket.
They can't create tickets for users.
FML

Just another day in corporation.

Screwdriver followup ticket, day three. No progress made, no fucks given.

I am tired.

Best fuck QA ticket. "Images are not loading good." No page. No more info.

What am I suppose to do? Test the whole fucking site.

JIRAAAAAAAAA

Ticket : "I have a blank page when I load this page"
I open the script (php), I see at least 7 nested foreach loop starting with a 2600+ long array. I spot the buggy loop. I mark the ticket "may need refactoring". I go drink a beer with colleagues.

JuniorDev: <<moves bug ticket to 'done'>>

FullStackClown: Ah nice, let's see what they've written here as to what the problem was <<reads comment in ticket>>

JuniorDev's Comment: "👍"

FullStackClown: 🤦‍♂️

Here is your ticket.

1. Mailserver is down.
2. Write a ticket to provider.
3. Can't get a reponse because of 1.
4. ?????
5. Profit
6. Scratch that. We're a start-up.

One day I created a bug issue for intellij to the JetBrains guys. After some days this ticket got closed with status 'fixed'. That was kinda satisfying.

Every Group Project in CS Major
Group 1:- Hey group 2 what project are you making ..?
Group 2:- Can't tell , Top Secret

FINAL Day:-
Group 1:- Railway Ticket Booking System
Group 2:-Railway Ticket Authorization System

Evaluators :- I think I saw similar idea somewhere....😂

Today I got a ticket.
Last comment:”It’s urgent.”
Scrolled down the tickets history. Opened 21st March 2020
I joined them company July 2020

Client: the app is slow
me: can you upload a thread dump to the ticket?

Client: here *uploads 2GB catalina.out.gz*

Adios Motherfucker!
Finally got that pile of misery finished. That simple ticket exploded in complexity and had quite a bit of scope creep. So so glad it's over. I mean, apart from code review and QA. But still. It's done!

Also: I may have been drinking already. Clearly not enough from the painful lack of typos and silliness. Gonna go work on that.

A group of programmers and marketers were traveling to a trade show on a train. Each of the marketers had bought a ticket, but the programmers had only bought one ticket for the lot of them.

One of the programmers was keeping a lookout, and when the conductor neared their car he called out "The conductor's coming!" and all of the programmers piled into the train's lavatory and closed the door. The conductor took the tickets of all of the marketers, and then knocked on the lavatory door and called "Ticket please." The programmers slid their ticket under the door, and the conductor took it and left.

The programmers were laughing at the marketers for the rest of the trip, and the marketers felt like idiots.

On the way back, the marketers decided they would use the same trick and only bought one ticket for them. But this time, the programmers didn't buy a single ticket! Again, one of the programmers kept a lookout for the conductor. When he called "Conductor coming!" all of the programmers piled into one lavatory, and all of the marketers shut themselves into another lavatory.

One programmer came back out of his lavatory, knocked on the other door, and said "Ticket please!"

Ticket: "I have questions about the system."
Nothing else. What are your questions???? Please tell me

* Urgent support ticket comes in.
* Switches to working on it.
* Urgent support ticket comes in.
* Switches team member to it.
* Urgent support ticket comes in.
* Gets dev team to help with it.
* Urgent support ticket comes in.
* Asks CEO to help on ticket.
* Urgent support ticket comes in.
* Cries.
* Urgent support ticket comes in.
* Prays to Mecca.
* Urgent support ticket comes in.
* ...

I then find out two more urgent support tickets are about to come in.

And then another one.

Help.

I iust won a fully paid ticket with flight and accommodation to a machine learning research conference later this summer! Yaay!

Coding is slowly starting become my ticket out of the military and allowing me to make a life for my family where we don't have to move every few years.

Dear project managers,

Learn to use the fucking ticketing system. And by "use" I don't mean emailing IT asking them to open a ticket for you.

#GrowUpPinheads

Oh man, today just gets better and better...

Manager: * Creates ticket, which has a link to a shared pdf, with each page being a link to another ticket in our JIRA with unrelated bugs of what we are currently working on. *

fullStackClown: I'm closing this ticket and putting this feedback in the original ticket that I assigned to you to review days ago.

Manager: Rages like a little baby and removes my access to said shared pdf.

fullStackClown: Welp, looks like I'm done for the day! Cheers!

Support elevates a ticket.

Ticket: customer is getting a weird error uploading photo.

Can’t recreate. Tell support to call them back. I’ll sit in on the call.

Watch the process. Noting extraordinary...

Hmm.

Me: can you get the customer to open the pic in photo viewer?

Support asks as much.

Support: uh, he says he gets a similar error opening this photo in the photo viewer.

Me: 🤦‍♂️ that is a corrupt file!

Went out with friends last night to celebrate a birthday, on our way back with the train we are asked for our tickets. We had bought a group ticket (for 30€/5 Persons) and showed it to the ticket checker. It was 6:20 am at that point and we were all tired and just wanted to go home, but apparently the ticket was only valid to 6 am (it does not say that anywhere on the ticket and it is called a "9-o'clock day ticket"). That asshole seriously made a record about all of us and took 60€ from everyone of the 5 of us.
The Deutsche Bahn company is the only rail company in my region, there is nothing that could compete with them, so they just shit on their customers. And now they want to privatize the highways too? Stop making public traffic something to pay for! There is no competition if there is only one traffic company with the only highways or train-web in a specific region.

Tester commenting in a Jira ticket:
"Not testable"

Me thinking:
"Why? 🤨 Has he been attacked by a tiger or something?"

Manager: What's your time estimate on that latest ticket?

Dev: It's literally written in the "time estimate" field on the ticket, even in standard human units like "hours", "minutes", and "seconds"

Manager: ...

Dev: ...

Me: *implements design given by client*
My boss: *opens ticket*
"This is not acceptable. this looks like a child made his first website"

k thxbye

With luck like this I'll be buying a lottery ticket next.

Just pushed my first ever ticket to production! AAAND on top of that, did not take down our entire system. 😅

When something doesn't work you open a ticket on the ticketing platform. Today ticket platform was not working: Ticket-Inception

My new favourite response to a bug ticket:

"But do you not remember we tested the implementation and it worked?"

... yes ... then it broke under other circumstances.

... must be terrorists or something

* Hit send on email *
* Realize you wrote Retards instead of Regards *
* Shutdown the laptop *
* Book a ticket *
* Move to another country *
* Start a new life *

Parked the car in a parking lot 15 mins before job interview. Plenty of time to spare.

Go to pay for parking.

Ticket machine doesn't accept cards. Fine, I have notes.

Ticket machine doesn't accept notes. Shit, I need to go get change quick.

FUCKING FUCKER DOESN'T ACCEPT £1 COINS WELL WHAT THE FUCK TO YOU ACCEPT THEN YOU FUCKING FUCK I'M GOING TO BE LATE FOR MY JOB INTERVIEW OR GET A £80 FUCKING PARKING FINE

My company's logic:

If your account gets locked, you need to raise a ticket using the company portal. In order to access the portal, you need to enter your credentials.

Error reporting in metro ticket....

I opened a ticket earlier with my automated ticket script, and saw its number, so I couldn't resist.

Ticket from legal department: implement GDPR recommendation, log customer consent, separate checkboxes to opt-in to T&C and newsletter

Ticket from marketing department: small print T&C on sign-up, remove "conversion killer" checkbox

This is why we need a product owner

Random Person in Company Slack: "Hi! Good Morning. How are you?"
Me (in my head): "Just raise a ticket...." 😓 😓

Boss told us to make a tickets app.

Tickets will have to_be_completed_by date

Devs in our team allowed that to be in the past. Because our manager consistently says he wants stuff done like yesterday!

When an estimated 2 point ticket turns into an 8, arghghghhgh

Touch Initialization failed!
No train Ticket for me :(

Got a ticket form a client reporting a calculation giving the wrong outcome.

In return I ask her what she thinks the outcome should be and why.

"The right answer because I said so."

Yeah thanks that's going to help a lot.

We started a project in January for which I was the sole developer, to automate tedious interaction with a vendor's ticketing system. We have a storage environment with about 400,000 commodity disks attached(for this vendor-- there are other vendors too), in sites around the US and Canada. With a weekly failure rate of about 0.0005%, that means about 200 disks a week need to be replaced.

This work-- hardware investigation through storage appliance frontends, internal ticket creation, external ticket creation, watching the external ticket for updates to include in our internal ticket --was all manual, and for around 200 issues a week, it was done by one guy for two years. He was hopelessly behind. This is all automated now, and this morning, I pushed this automation from dev/test to production.

It feels great to see your work helping people around you.

Conference tickets are overpriced

true or false?

Do you attend any without being sponsored?

QA ticket. Images are pixelated blah blah blah increase pixelation to make them pretty.

Next ticket: why is the site so slow. Need to be optimized blah blah blah

Today I closed my first support ticket! :D
It feels fucking good!

New ticket: Add Feature
description: (will be updated)

Last famous words before the creator went on vacation until app release

missed a plane. the first trip to my country is after 24 hours.. had to pay for another ticket..

yeah, welcome 2019

JIRA, the haiku (w/Bonus Dilbert strip)

Please make a ticket
Please move the ticket you made
Please tag your ticket

A previous project manager thought that by marking every ticket as high priority, they would get done faster.

// priorities

It's the end times: I've received a JIRA ticket asking me to fix something in JIRA

Customer submitted ticket today stating that his 404 page was missing ohh the irony

Colleague calls the IT support because he forgot his Windows login after the holiday.
IT Support: "Please go to the intranet and write a ticket" - telephone call ended.

"when you get a low priority ticket during a production outage"

Let's say you have a MySQL database table for jobs. Each job has 1 associated ticket. You want to keep track if the ticket is closed or not. Every sane person creates jobs table, tickets table, keeps bool value for ticket state and relationship between them.

But because our database is designed by a half braindead amoeba, we have one table only, so each job has to be updated individually with a new ticket number and its state. Beacuse it sooo much faster to update (daily!) 13k jobs than just 100 tickets.
As a bonus - if the ticked is closed, the column "ticket_closed" is "No", if it's still open the value is "FALSE". Yes, both as varchar/strings.

A company contacted me about their custom ticket system not working

Then after asking them couple things they just wanted me to look at emails they found stacked and lost in the ticket system archive:

One clients ticket somehow got caught in between updates and hes been answering the auto close notification (each ~3 days because it never got closed) of the system, with ranging from "yes, thank you, I have solved the issue" escalating to "why dont you leave me alone, I have told you, I have fixed it, please stop", poor guy 🤣

Dev: What is higher priority, ticket A or ticket B?
PO: No.

when a QA opens a ticket for you!

New ticket:

Ticket: "I just spoke with-"

Me: "LET ME STOP YOU RIGHT THERE! IM NOT GONNALET YOU FINISH! IS THERE A PROBLEM? THEN HAVE THE PERSON YOU SPOKE WITH / SAW THE FUCKING THING HAPPEN CONTACT ME! ALMOST NEVER IN MY LIFE HAS A GAME OF TELEPHONE EVER DONE ANYTHING BUT FUCKING DRAGGED OUT THE PROBLEM! WIDGET DOESN'T WORK? THING DOESN'T DO A NON SPECIFIED THING? FUCK YOU FOR DROPPING ALL THE INFO I NEED AND SENDING A VAGUE EMAIL!!!"

-ticket set to not gonna do shit until someone who saw the thing gets off their ass and says what is actually happening-

Classic support ticket:

Me: "Uh... those numbers in your screenshot look right"

Customer: "Well it wasn't yesterday, looks like it is fixed now"

Me: "...."

-closes ticket-

First time committing a ticket is scary… I can’t stop thinking how my colleagues and tech lead gonna look at my code and question me if I lied on my resume…

Fuck NYC....just got hit with a fucking parking ticket for double parking. $115. *sigh* *pets cat in sadness*

Just closed a TOP PRIORITY ticket with "as designed"..

After a 1 minute talk with the developer who wrote this code, I found it is actually deliberate..
So I just closed the ticket..

but what really bothers me is:

That developer, is sitting right next to the QA.
HE IS SITTING RIGHT THERE..

We are a small startup company, everyone are sitting around the same table..

communicate much?

When every single JIRA ticket is marked "Critical"...

Dear customers just fucking stop and do the following:

1. Explain yourself in complete sentences.

2. Read the email you just wrote.

3. Regardless of the content delete the email.

4. Go about your day and leave me alone.

Fucking emails like this, I can't even:

Customer Person A: Hey this thing doesn't work when I change X!

Me: Uh where did you change X? There's 3 places that can be changed.

Customer Person A: No, Customer Person B is responding to the wrong ticket.

- Customer B has never responded to the ticket and isn't on the email chain we're talking about...-

-ticket closed, communication impossible reason "Kiteo, his eyes closed"-

So, I got a ticket to make a page using a given wireframe that had submit buttons and other buttons to add more items in the wireframe.

So, I pull the html, hook up the abilty to submit the form and add items, and send it out for review.

One comment on the review.

"Remove the functionality, you'll handle it in the next ticket"

So I commented out the javascript. Guess what I'm doing on the next 10 minutes.

Worst Jira ticket I've ever seen:
Title: "It looks f#?$ed"
Description: ""

This gem was opened by the project producer. When asked about it, it was just a mismatch in text margins.

Thank you, dear 3rd party vendor replying to my ticket to my work email and sending me my new password IN FUCKING PLAINTEXT!

while true; do
echo "Drop everything this $LATEST_TICKET is your highest priority now!"
sleep(3600)
done

When you solve a major-ranked ticket with a single line of code.. You feel like..

The new ticket / check-in terminals of the local busses apparently run on linux 😃
(Sorry for the bad pic quality)

Just got a ticket reassigned to me from another employee leaving the company. The "Days to Due Date" field says -964.

It's for a very simple task that takes max 2 hours. Contacted the guy who created the ticket and it's still needed.

Excuse me what the fuck.

Email (not a ticket) comes in this morning: "You need to make X change to y thing, yesterday!!" with of course the obligatory million + 1 Cc's including unrelated directors across multiple sites.

Me as my helpful self: I expected this request, I'll get it sorted asap

Director 1: *calls*
Me: I'm working on it

Manager: *calls*
Me: I'm working on it

Submitter: *calls*
Me: ignore

Director 2: *calls*
Me: I'm working on it

..............

As a bonus rant, after implementing the change, manager calls and criticises my technical explanation to the submitter who I know is fully capable of understanding the way it was explained 😂

Happy Thursday!

New AD account.
cannot login.
Want to create a ticket.
Need a login to create ticket.
*genius*

Go to coworkers machine.
Open ticket there.
They respond, the user must create the ticket himself.

Ffs!

When your PM files a ticket saying "make better use of space" on your UI feature

WHAT DOES THIS MEAN??

when you have to use the bathroom but you just keep telling yourself "I can finish this ticket in like 5 minutes tops"

30 minutes later... still haven't gone

I'm taking a vacation in two weeks to hopefully recover from this burnout. I don't know if I can make it that long.

I've been trying to work on a ticket for the past two days. I don't even know what the ticket says. Just something about optimizing the Google pay object api. idk. I just can't. I need to have it done today though. Bleh.

Lotus Notes is absolutely the worst platform known to man. Every time a ticket comes in I want to set the Domino servers on fire.

I just want to make it clear for all the PMs out there...

If you don't put it in a fucking ticket, or don't mention a feature you want in a ticket, I will not do the work or forget put something into a feature.

Write that bitch up if you want it done.

Alright lets install PHP7 :D
6 hours later....

Opens a support ticket: Screwed up everything !

When an analysts opens a ticket about a wrong result csv file but instead of putting the actual file there , he puts a screen shot of it

Explaining why I need something installed on my work laptop in a request ticket: BECAUSE IT LOOKS COOL

I work as a customization and integration developer. Two months ago a customer opened a support ticket with an issue they encountered. I fixed it and released the new package. Today they opened a new ticket on the very same issue. Turns out they never even installed the fixed version.

Mark the ticket as user error and hope I don't see it again...

Saw a rare moment. Maybe I should buy a lottery ticket? It might be a winner :)

So you remember the old, not so good days, when your app worked in all the browsers besides stupid Internet Explorer?

So I through those days were long gone, and today ticket that functionality doesn't work in Edge.

Good part of the story? Ticket number is 666.

A regular russian trolleybus (electric bus, a really old and popular way of public transportation). A ticket is ~70 cents, fixed fare, accepts Apple Pay / Google pay / Samsung pay

The all-times USB problem: SOLVED. Ticket closed.

This was the entire ticket.

DevSup channel:

Someone: FYI, Db is down(ticket link)

Otherone: Can anyone help me connecting
with db? I am having issues.

I am so happy I am leaving this place in 2 months.... 😂😂

A newish client just sent a channel ticket marked as "urgent", which set off the alarm for everybody in the chain, with an amazon link to lingerie.

I seriously don't know how to react to this, since I really hope it was a mistake and not how he expects us at the next meeting lol

To send such a ticket you have to confirm your pin and confirm the urgency reason too by the way, so the only thing coming to my mind is, it was some sort of clipboard fail?

Getting "bug" tickets from customers complaining about EXACTLY WHAT I DESCRIBED WOULD HAPPEN. THATS NOT A F&)$*(%$(*# BUG, THATS LITERALLY WORD FOR WORD WHAT I WROTE IN THE TICKET LAST WEEK YOU F&#*(@#$() NEANDERTHAL PIECE OF SH$%*(#(*)!!! WE AGREED ON THIS EXACT BUSINESS PROCESS WEEKS AGO. DO YOU EVEN READ THE WORDS THAT I WRITE AAAAAAAAAAAAAAAAAAAA

Support Team Member opened a ticket.

> This customer's image isn't loading.

Load image, it's white and transparent on a white page.

> Be me
> Using another country's public transit system for the first time
> QR reader can't read my bus ticket
> Ask the bus driver about it

"Sir, can I check myself in here?"
"Very high-tech system, isn't it?"
"Sir, I'm a programmer..."
"Shitty system then? Maybe you could fix it?"
(thinking: you're not paying me for this you bastard, and if you want me to get a manual for this piece of shit to repair what should've worked in the first place, you're sorely mistaken...)
"Probably I'm the kind of person who would... Anyway the ticket is valid."
I didn't bother checking the ticket afterwards.

All I wanted to do was get on your bus mate 😐

Ok, I am actually losing my mind at this bad excuse of a work place.

This guy, that I had only briefly talked to in email twice before, never met or even had a video chat, opened a ticket like this:

"Hi Alt-Tab,

I hope you enjoyed the end of last week, the weekend, and the beginning of this one! All well here. I ventured to [random place in London] for the first time on Saturday – liked it."

Now. I already can't fucking stand when colleagues that are not at all close start emails with "how was your weekend?" shit because then I have to waste another minute addressing that. But this guy took it to such another level that I literally had to read his email 3 times to believe what I just witnessed.

And of course he then went on and described the issue as folows:

"Just a quick note about the issue I have - could you let me know why the calendars are not syncing?"

Maybe if you fucking spent half of the energy of you writing a polite bullshit "hello" and instead used that to actually describe the issue I could help.

Fuck off.

And the award for the best ticket if all time goes to:

"Create script"

No open questions. Of you don't understand, are you really a dev?
In all seriousness, this thing was in the board for like 3 days and nobody raised any questions...

Submitted a ticket to the 3rd party IT provider today. Just like they always do they close the ticket instantly saying they did the work when they didn’t do anything.

Except this time they went one step further. They documented that they had a conversation with me and that they convinced me that I didn’t need the work done.

No such conversation occurred. I have not changed my mind nor have been given any reason to. They just want their ticket times to appear as fast as possible and are willing to lie through their teeth to achieve that.

Prepare for a shit storm motherfuckers.

0. The conference room TV has no sound.
1. I submit ticket to Facilities.
10. Facilities closes ticket saying that's up to Service Desk.
11. I submit ticket to Service Desk
100. Service Desk closes ticket saying that up to Facilities
110. ???
111. Profit

Bug fixed! Commit, close ticket.

Ticket reopens. Dang.. let me test it. Still fixed, wtf? Send message to QA guy that opened it again.

"Read my comment." Comment has some entirely different yet slightly related bug.

Leap out window.

Convo with manager "ticket is a month late"

I've been on holiday for 3 weeks.

2 months into my first dev job, everything looks like a Jira ticket now.
Mum: wash the dishes
Me: create a ticket for that... i estimate the story points to be 2

people will write an email but wont update JIRA ticket

Joined as an Intern at an MNC, There was an issue with creating the account so a ticket was raised. Now to view the ticket, I have to log in the account :)

Getting a ticket that a feature is having problems when you triple-click it. Otherwise it works fine.

I'm so close to write them simply back: "Then don't fuckin do it?"

Not fired, but shot by my college, if I create a ticket that our software-ui isn't rendered correctly with font size 72

Just casually working on a bugfix ticket

Random code review:

contractor changes 2 lines in the .gitignore and 1 line in the composer.json and logs 4.5h against the related ticket .. hmmm

The shitty trainticket-app doesn't sell me any tickets. Who the fuck coded this crap. I really tried hard to pay for a fucking ticket...

I said “Thank You, Machine” after it scanned my ticket and let me through.

Meme quoting one of our employees who sent in a ticket asking if something was a "phishing technique without the use of email."

So I was just informed I have 40 tickets with my name on them. No big deal normally except that I had no idea and was scheduling based on the fact that I knew I had 25 on my plate and most of them were OBE. How did I find this out you ask? Well rather than updating the tickets in our ticket tracking system, my PM updated a spreadsheet that is out in no man's land. So it looks like I have been doing no work for the last 3 months when in reality I have been busting my ass to get shut done and fixed. Why even have a ticket tracking system?

CTO: We can't keep getting egg on our face letting these simple mistakes through. We value your expertise, please speak up.
QA: This looks fucky, should it look this fucky?
*crickets*
Dev: That is dangerously fucky.
QA: Ticket time.
PM: Hey Dev, I know it's not your AOE, but I need to assign it, and you spoke on it so here's your ticket.
Dev: *dies inside*

Someone blocked access to AWS RDS database and for the past few weeks I can't access the database from my machine when connected to our company network.

Created support ticket to internal IT team and someone closed the ticket. I re-opened the ticket and in the comment someone wrote "Their team doesn't handle AWS access".,

Wrote email to the director of infrastructure and that asshole replied to me asking some questions and after that his been ghosting me for past 2 weeks.

I'm tired and I don't have energy to do any more follow ups.

*Log in to work*

*Get a ticket to work on*

"Oh this seems like a simple fix. This should be done in a couple hours."

*Move the ticket to Completed status*

"Oh would you look at that. It's 9 PM and now I have to make dinner".

One of the great joys of being a dev.

Recently, one of my customers filed a ticket because some iFrame he got from another company wouldn't display after putting it into the content editor.
I told her it won't work because the (third-party) editor prohibits JavaScript inside iFrame tags and their attributes for security reasons.
She said ok. She said she'd understood the problem. And then, she reopened the ticket four (4!!!) times for the exact same reason, once because she tried to use a fixed iFrame tag the other company sent to her... still containing JavaScript, of course.

But, yeah... She understood what the problem was. Is clear.

So there was one plus invite sale today in India !
I think the ticket were sold out early!
Then there is this guy in twitter 👇

If you're filling a ticket on a team, make sure it includes EVERYTHING that is needed to complete the ticket so anyone on your team can complete it, not just the people with institutional knowledge.

I haven't felt an urge to post on here in a while just because things have been going so well. But this month, is just not that kind of month anymore.

I'm upset. I'm upset by how I've been uprooted from my routine. I know I shouldn't be that bothered by it and things always change. But what the fuck is this company thinking to be using it's own fucking home baked ticketing system!

WHAT THE EVER LIVING FUCK IS THIS SHIT!

Let's go over the issues it has
1. I can't fucking email my clients through it
2. all emails are not recognized automatically. In other words each new email creates a new ticket if it does not have the tracking number attached to it.
3. I have to fucking hunt around in my inbox that is now bombarded by every email that is created for this ticketing system. Slap on a fucking tracking number. And then HOPE TO FUCKING GOD that the person on the other end doesn't erase the subject and cause the system to create a new ticket just for it.

Let's go over Zendesk which they've decided to decomission.
1. I. DON'T. HAVE. TO. DO. ANY. OF. THAT. FUCKING. SHIT.
2. That's it. It's fucking simple

Seriously. They forced me off of my original platform because this company already had a "ticketing system", if you can even fucking call it that, working.

And just if you weren't aware, all of this change happened because my company got bought out. It got bought out by this behemoth company that isn't willing to let me continue using a system; that has been very efficient, mind you, and instead make me use their system.

I. FUCKING. HATE. THIS.

Every fucking day! I have to do this stupid bullshit of emailing clients from my personal work email instead of on the direct ticketing system.

When I first started using this thing I actually thought I could use it to email the clients. For a solid two weeks I was "communicating" to clients through their ticketing system. Only to find out that the entire time those clients were not getting my actual fucking email! WHAT THE ACTUAL FUCK?

Then these guys tell me after the fact. "Oh that's strange... We never noticed that you can't send emails through it... We always just had used our work emails."

Are you fucking jerking my chain! You guys have literally been sitting in this slimy pit of hell for so long that you don't even know there are better options out there!

You don't have to fucking live this life!!

I don't think I'm going to make it. Something needs to change. And I know upper management isn't going to do it, because I fought hard to try and keep Zendesk. They are not keeping it. After this next quarter it is officially gone.

I'm trying to think of coding solutions to make my situation better... But I shouldn't have to fucking do that! There are perfectly good working solutions out there, and this company doesn't want to budge because "that's the way we've always been doing it"

I'm going to fucking rip out my hair.

This is the kind of company that provides online ticket sales for one of the bigger cinemas in Italy. Yes, registration is unavoidable.

Talking about Deutsche Bahn ticket buying not working, but the NS sends me emails with non-functional buttons to press in order to get my ticket. What a train wreck

Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.

Moves to QA environment, the original bug reporter tests and *passes* the ticket.

Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.

Apparently our the workflow is -

Code->QA->Staging->Requirements

Makes sense! :)

PMs that start every ticket with "as a user I..."

Customer CCs me and some other devs:

"Why isn't there a support ticket on this? I didn't get an email about a support ticket opening!!!!!!!!"

-check's email-

To: donotreply@......

¯\_(⊙_ʖ⊙)_/¯

Today I learnt that I'm much more productive if I get a constant loop of feedback on my tickets and stuff. Feels better that way.

Edit: I'm working with a new coworker from QA and she's more responsive than the others. I get my feedback fast and timely and this makes it way easier to work

Using ALL CAPS on subject line of your helpdesk ticket, isn’t going to have it actioned any sooner!

Ready for another look into my JIRA life?

Ticket Title: "The 'Selected photos' setting will result in users being able to select only one photo at a time."

Ticket Description: "This is not directly a bug, because this problem is caused by the selected setting. Here one would have to consider to give this option no more and/or with an error message the user on it to make attentive, how he can change the attitude."

I don't even have to worry about NDA in this one because it makes absolutely no sense.

BTW, we don't have a single text in the app with the words "selected photos"

99% sure the creator of this ticket wrote it when they were high, drunk, or both

me: reviewing an old ticket relevant to testing a similar area of a ticket im working on as a developer

"QA Note

Please don't ask me where to find one of these, because I don’t know"

the retired QA who worked on this ticket also didn't write where to find the thing

well fuck me alright

So... I take over this one ticket to test... the ticket mentions some visual component popping up when a button is clicked. It says there is a success and a failure message. The title of the story also mentions another functionality.

I start testing and some fellow QA asks me why I'm testing in this environment. Turns out, three people are sharing one environment and three different things are deployed...

I ask the dev whats going on because I heard there are multiple people deploying stuff...
He just tells me "oh, my changes are deployed I just checked".
I tell him that it's not about that but about communication and testing one thing at the time. Then I tell him, that I wouldn't test until his stuff is the only stuff there.

Some time later he hits me up again, now with the env to himself.

I test and quickly I see, that there is only the positive message even when I make sure that the backend is not reachable. I tell the dev what I found and he tells me "oh no, it's just the implementation of the popup thing, it's just frontend for now"...
I tell him, that the ticket should say so.
No answer for like 1-2 hours. Then I get an "ok".
End of the day.

Next day I come in and the fellow QA tells me, that the dev asked him to test the ticket.
I ask him if he changed anything about the scope of the ticket, he says no...
I'm like "ok... know what... begin testing and then tell him what I already told him".
So he's testing and then tells him again to update the scope.

Later in the daily the the dev's update is besically "they won't test my ticket..."

It would have taken him like 1 fucking minute to update the ticket...

The whole QA team was always trying to being helpful and even when the tickets where sometimes not 100% clear we always made it work... but now we are more and more going towards "MR does not meet ticketdescription, fix it" and "I don't care if its just a small thing... fix it and then come back to me"...

Seriously frustrating some times...

Having 36 jira ticket open and people continue to contact you on micro$oft teams =_=

Got this design for a button.
Now I'm writing an essay in the ticket about how this is problematic for localization and accessibility.

co worker edits front end to design, breaks code then files a bug ticket for you.

Story Time: About Priorities and Sales

So at this point I'm working tech support for a company that makes some super cool networking equipment, think big data / data centers and such.

This company had grown at a good pace but the the support team had not (thus is the way for all tech support evetually). So I get a call from a frantic sales guy:

Sales: "OMG, where are with this ticket?!?!? It's a P2 ticket!!!"

Me: "Well the ticket came in 30 minutes ago, I emailed them some questions, but just so you know I have 8 P2 tickets, and 4 P1 tickets.... so it will be a while."

Sales: "OMG! Make my customer's ticket a P1!!"

Me: "Sure."

-call ends-

-30 minutes passes-

-sales calls again-

Sales: "OMG, where are with this ticket?!?!? It's a P1 ticket!!!"

Me: "Well I haven't gotten to them yet... just so you know I have 7 P2 tickets, and 5 P1 tickets.... "

Sales "ARGH!"

ʅ（´◔౪◔）ʃ

[slack]: here's a nice workspace name. Let's take it.

Workspace started to be unusable (constant refresh). Ticket sent.

[us]: We should delete it and create it again.

Few minutes later - workspace name unavailable. Ticket sent.

(48h later)
[slack]: my precious!!!

Our favorite ticket system blokes are back with a big fat update for their software.

What changed?
All workflows are fucked because everything is somewhere else suddenly!

Half of the features suddenly stopped working!

Variable formats in forms have been changed from {} to [] without reason, migration or warning! Sorry, {Username} ¯\_(ツ)_/¯

Half-assed features that don't work half of the time have also been added!

Fucking great!

Who beta tests this shit? Nobody?