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.

And then assign it back to them requesting they specify all the details so it can be groomed in the next scrum (hahah)

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. 🤦‍♂️

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?"

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.