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.
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’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.
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 get X bugs per sprint, and I closed on 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…