Automation Rules: Stop Chasing Testers for Missing Info

Every bug tracker has the same quiet problem: incomplete reports. A tester submits a crash from Discord, no logs attached. You notice it an hour later, write a follow-up message, wait for a response. Meanwhile ten more reports came in, three of them also missing attachments.

This is exactly the kind of work that shouldn’t require a human.

Automation Rules let you define conditions and responses once, then let BetaHub handle the follow-up. No developer intervention needed.

What it does

The logic is straightforward: when a bug comes in, a matching rule fires. The system waits however long you’ve configured (giving the tester a chance to add attachments themselves), then checks a condition. If the condition is met, it takes action.

That’s it. Trigger → delay → condition → action.

Currently, rules fire on issue creation. You can scope them to specific tags — or leave them open so every new bug triggers the check.

Two scenarios that show why this matters

Scenario 1: crash report, no logs

Your game crashes. A tester reports it on Discord. No log file attached.

Without automation, someone on your team eventually notices, writes a message, waits. With a rule in place, BetaHub waits 60 seconds after submission, checks whether log files are present, and if not — sends a message directly to the reporter on Discord:

📄 Log file needed for #1847 Game crashes to desktop right after the loading screen on level 3 in Dev Project

Use the Upload Files button below, or upload here on the web.

The tester replies with the file attached. The bug report gets what it needs. Nobody on your team had to do anything.

You can filter this rule to only fire for bugs tagged as “Performance - Crash” (which BetaHub’s AI assigns automatically), so you’re not bothering people about logs on minor UI issues.

Scenario 2: platform-specific testers, wrong device data

You’re running a multi-platform beta. Your Discord server has a “PS5 Testers” role. Testers keep forgetting to select their device when submitting bugs — or select the wrong one.

Set up a rule: when someone with the “PS5 Testers” role submits a bug, automatically assign “Console — PlayStation 5” as the device. Delay: 0 seconds. No condition check needed — if they have the role, they’re on PS5. Done.

One rule per platform, and your device data is clean from day one.

What you can configure

Conditions:

• No attachment — checks whether logs, a screenshot, or a video is missing
• Reporter has Discord role — checks whether the reporter holds one or more roles in your Discord server

Actions:

• Ask user for details — sends a follow-up message via Discord using a customizable template
• Assign device — sets the device on the bug report automatically (supports consoles, PC, mobile, VR headsets, and more)

Message templates support variables like {{{title}}}, {{{issue_url}}}, {{{tag_names}}}, and others — so your messages can reference the actual bug rather than sending something generic.

Before you set it up

Automation Rules require two things:

1. Automation Tasks experimental feature enabled — find it under Settings → General → Experimental Features
2. Discord Bot connected to your project — required for message delivery and role-based conditions

Once both are active, go to Settings → Automations and click Manage Automation Rules to create your first rule.

Full configuration details — including the complete list of template variables and supported device types — are in the Automation Rules documentation.

One tip before you start

When building a rule that asks for attachments, use a delay of 60–120 seconds. Testers sometimes upload files right after submitting — give them that window before sending a follow-up. For device assignment rules, 0 seconds is fine. There’s no reason to wait.

---

At BetaHub, we empower game developers and communities with an engaging platform for bug submission. We foster collaboration, enhance gaming experiences, and speed up development. BetaHub connects developers, testers, and players, making everyone feel valued.