Quick answer: Remote bug bashes lose the energy of an in-person session unless you structure them. Discord Stages with a shared tracker board recreates the rhythm at a fraction of the coordination cost.
In-person bug bashes work because everyone's in the room. Distributed teams can replicate the rhythm with a Discord Stage and a synchronized tracker.
Stage channel as the room
One Discord Stage. Mute by default; raise-hand to share a repro. The audio creates the 'in the room' feeling that text chat doesn't.
Shared tracker on second screen
Bugnet board (or any kanban) open on a second screen. New tickets land in a 'bug bash' column; everyone watches the column populate in real time.
Engineer-on-call in the Stage
One engineer present to triage live. Sev-1 lands → engineer raises hand → quick 60-second discussion → assigns or de-prioritizes. The Stage is the triage meeting.
Time-box hard
2-3 hours, then end. Distributed teams will fade after 3 hours regardless of format. The energy is finite; don't dilute it.
“Distributed bug bashes need explicit choreography. The lack of structure that works in-person doesn't translate.”
Record the Stage's audio (with consent). Reviewing flagged repros later catches details that the live triage missed.