Automation Rules: Stop Chasing Testers for Missing Info

In short: Automation Rules follow up on incomplete bug reports so your team doesn’t have to. Each rule runs as trigger → delay → condition → action. For example, a rule can wait 60 seconds after a crash-tagged bug arrives and, if no logs are attached, ask the reporter on Discord to upload them. Another can set the device for testers with a platform role.

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, missing 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.

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 attachment condition 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
• Reported from Discord channel — checks which Discord channel the bug was reported from
• Content matches — checks the title or description against text rules (contains, doesn’t contain, equals, shorter or longer than a length)
• Matches LLM prompt — AI judges whether the report fits a built-in check (incomplete report, gibberish, off-topic) or your own instruction. Uses your plan’s monthly AI allowance.

Actions:

• Ask user for details — sends a follow-up message via Discord (or by email, for reporters who aren’t on Discord) using a customizable template. You can specify which fields to request (logs, screenshots, video, steps to reproduce, or device info) and mark each as optional or “only if not already provided.”
• Assign device — sets the device on the bug report automatically (supports consoles, PC, mobile, VR headsets, and more). It only fills an empty device and never overwrites one the tester chose.
• Assign tags — adds tags to the report
• Assign release — sets the release to the latest published version or a specific one
• Archive — removes the bug from the active list (reversible)

Rules can also be configured to run (or skip) on issues that are auto-classified as duplicates.

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

Before your first rule:

1. Enable the Automation Tasks experimental feature under Settings → General → Experimental Features.
2. Connect the Discord Bot if your rules message reporters on Discord or check Discord roles or channels.

Then 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.

Common questions

What can a rule check and do?

It can check for a missing attachment (logs, screenshot or video), the reporter’s Discord role, the Discord channel the bug came from, text in the title or description, or an AI judgement such as “too vague to act on”. It can then ask the reporter for details, assign a device, add tags, set the release, or archive the report.

What do I need first?

Turn on the Automation Tasks experimental feature (Settings → General → Experimental Features). Rules that message reporters on Discord or check Discord roles or channels also need the Discord bot connected. Then go to Settings → Automations → Manage Automation Rules.

How long should the delay be?

60–120 seconds when asking for attachments, since testers often upload right after submitting. 0 seconds for device assignment.

Can a rule apply only to some bugs?

Yes. Rules can be limited to specific tags, such as “Performance - Crash”, and set to run or skip on detected duplicates.

---

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.