I'm probably just bad at agile but I usually prefer if QA sends a quick message about a bug first to make sure it's actually a bug and they're not just misunderstanding a story.
this post was submitted on 27 Jun 2023
464 points (99.2% liked)
Programmer Humor
32410 readers
224 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
That seems perfectly reasonable.
What comes to mind when I see this meme is more along the lines of CS DMing devs directly with customer issues and expecting us to magically come up with a solution to something with minimal information given.
I love those because they close so quickly. Everyone gets X bugs per sprint, and I closed one in 30 minutes. One less thing to do this sprint.
Or it's because every time they make a ticket it's so messy it can't be understood.
Of course the grizzly way to respond back is to reassign it back to the QA and demand clarity and reproduction of the issue.
That ain't very grizzly. We have a "need more info" column in our support trello and nobody has a problem with it.
You'd be surprised at how many folks take it personally...
Jira plugin FTW.
Right click their message - create a ticket from this message.
And then assign it back to them requesting they specify all the details so it can be groomed in the next scrum (hahah)
And then you close the ticket and mark it as wont do because they dont know what they want and the details dont help
for OSS projects, it's "ping the dev on Discord"
I recently came across an early access game with no bug tracker where the expected way to report bugs was to leave a message in a discord channel. 🤦♂️
Whats a better way? Maybe some in game messaging system?
Literally any actual bug tracker.
I thought this was supposed to be funny, not a headache-inducing reminder of real life.
And usually it's your boss doing that so it's not like you can just ignore it till they file a ticket.
As a boss, if it's not important enough for me to take the time to make a ticket, I'm not gonna get that mad at the pushback. But then, I'm in a small company so if it is important my response might be "I have another 7 hours of meetings ahead of me, could you pivot to getting replication and add a ticket, and then assign it to yourself?"
For me instead of slack it’s the emails.
Honestly that just shows bug report templates/rules are too hard for most users.
Folks want to offboard their issue somewhere with minimal effort. It's much easier to do that in free text in an app you're already in than to submit a form where you have to categorize your issue on a website you'd have to pull it.
You're right to say it's friction making people step outside the preferred path.
People are lazy.
How about no
Don't forget bug reports that come in via email and Teams calls!
Steps to reproduce: Click the thing
view more: next ›