How to run a live bug bash

A live bug bash is the bug bash process with a clock everyone shares: same build, same hour, findings visible while people still hunt. This page is the live layer — join link, roster, board — not a replacement for charters or a known-issues list. For async-only review, see live vs async QA.

What “live” changes

Kickoff and recap already wanted a room. Live adds a roster you can see (who is recording, who is reviewing) and a board that fills during the hunt instead of a folder of files after.

Testers should not need an EveryBug account. A display name on `/bash/{slug}` is enough. Organizers stay signed in and own triage, duplicate marks, and tracker export.

Before you share the link

Do the same prep as any bash: build URL, charters, known issues, stager, moderator. Then create the bash in EveryBug, copy the contribute URL, optional PIN if the link might leak.

Tell people how to capture: in-browser record, upload a file, extension, or widget. One log — the board — not Slack.

• Freeze the build and seed accounts (same as the playbook).
• Write charters so login is not everyone’s first hour.
• Decide severity scale (blocker / major / minor / nit) before kickoff.
• Name who will export to Jira after triage — guests cannot push trackers.

During

Ten-minute kickoff: link, PIN, charters, known issues. Hunt 60–90 minutes. Moderator watches the clock; stager watches the env. Testers log as they go with expected vs actual and a clip or timestamp.

If two people hit the same bug, mark a duplicate on the board rather than arguing in chat.

After

Recap 15 minutes from the board: counts, launch-blocking, skipped charters. Deduplicate. Push to Jira/Linear/GitHub or export CSV. Close the bash when you are done — or let the end time auto-close.

Recordings remain in the bash project if someone needs the full file. The board is what engineering should see first.

Live bash, step by step

1. 1. Create the bash From Projects, start a bug bash. Keep the generated three-word name or shuffle while it is empty. Set start/end, optional PIN, charter and known-issues text.
2. 2. Share the join link Send `/bash/{slug}` (and PIN if any). Testers enter a display name. No account required. Organizers stay on the dashboard.
3. 3. Hunt on one board Testers record or upload, mark bugs with severity, expected vs actual. Findings appear on the board. Roster shows who is recording or reviewing.
4. 4. Triage and export Deduplicate, confirm severity, then send selected findings to Jira, Linear, or GitHub. Recap from the board, not from a Slack export.

Start a live bug bash free

FAQ

How do testers join a live bug bash?

They open the bash URL, enter a display name (and PIN if set), and can record or upload immediately. They do not need an EveryBug account.

What is the difference between a live bash and uploading videos later?

Live uses a shared clock and a board that fills during the hunt. Async upload still works in the same project; you still need a triage deadline so it remains a bash.