Quick answer: A bug report prompt that asks one good question gets richer detail than five generic fields. The right prompt depends on game state at the moment of the report.
Asking 'what happened' gets summaries. Asking 'what were you trying to do?' gets repro steps. Same player; different prompt; different signal.
Contextual prompts
In combat: 'What enemy were you fighting?' In menu: 'What were you about to do?' The game knows; ask what it knows you don't.
Defer detail
'Thanks. One more question: what should happen?' Two-step beats one wall-of-text. Players answer both; second answer is the real value.
Use checkboxes for known issues
'Did the game freeze? Did the screen go black?' Checkboxes are faster than typing. Players who would have shrugged check a box.
Always allow free text
Even with structured prompts, a free-text field captures the unexpected. The most important reports often start with 'I noticed that...'
“Prompts are conversation. Generic prompts get generic answers.”
A/B test prompt variations during the beta. The variation that produces more actionable reports wins; players don't notice the change.