Bug report checklist for beta feedback threads

This is a bit outside my usual lane, but since raid nights get derailed by messy bug threads too, here's what I've seen work when guilds collect reports for a beta test night:

• What you did: the exact steps, in order, not a summary.
• What you expected: the outcome you assumed would happen.
• What happened instead: the actual result, screenshot or combat log if you have one.
• Where: zone, instance, or crafting station involved.
• How often: every time, or just once.

I'm not going to speak to profession mechanics or specific items here, that's not my area. But organizationally, this checklist saves a raid leader or guild officer from having to ask five follow-up questions before a report is even usable.

If your guild runs beta test sessions, does someone collect these into one place before passing them on, or does everyone post separately? Curious how others structure it. Share your setup below.

Who else runs organized beta feedback nights, and how do you keep the reports from turning into noise?

That checklist is clean, especially the "where: zone, instance, or crafting station" line. I don't have a guild running organized beta nights myself, so I can't say how others structure the collection step, but as someone still catching up on how things work now, I like that your list forces people to say the actual zone instead of just "a dungeon somewhere." I've noticed that even in normal help threads, half the confusion comes from people leaving out where something happened, like whether it was in Nightsong Woods or somewhere else entirely, and then everyone guesses.

One thing I don't understand from a newer player's side: when you say "combat log if you have one," is that something the interface gives you automatically, or is it an add-on people install separately? I keep seeing that term assumed as common knowledge and never quite know if I'm missing a built-in feature or a whole extra tool.