Features

Discord Bot

BetaHub enhances project management by assigning a dedicated Discord bot for each project. This bot is capable of:

• Collecting bug reports from users by using the /report command.
• Automatically capturing bug reports, including screenshots, video clips, and log files based on the conversation.
• Broadcasting announcements of new releases.
• Facilitating interactions with your community regarding their previously reported bugs.
• Asking the user for additional information about a bug report (by using Ask For… buttons on the bug report page).

Our bots can proactively engage with users through direct messages, threads, seeking further details about a bug, requesting screenshots, videos, or log files. This process can be manually triggered by the developer or automated through our AI.

Bug reports from users can either be intentional, via a command, or automatic, identified by our AI through conversation analysis.

Step-by-Step Setup Guide

To deploy a Discord bot for your project, execute the following:

1. Go to BetaHub.
2. Choose your project.
3. Select ‘Settings / Discord Bot’ from the left-hand menu.
4. Verify your setup using /info command. Check the help using /help command.

You will be guided through a three-step process to configure your bot for the selected project. Complete these steps to get your bot operational swiftly.

Required Permissions

The bot requires the following permissions to function correctly:

• View Channels - To browse your channels list to identify the bug report channel.
• Send Messages - To post bug reports and other messages.
• Send Messages in Threads - To create threads for bug reports.
• Create Public Threads - To create public threads for bug reports.
• Create Private Threads - To create private threads for bug reports.
• Embed Links - To embed links in messages to provide visual information to the bug reporters.
• Attach Files - To attach screenshots to new releases announcements.
• Mention Everyone - To notify everyone about new releases.

Setting Up Bot Permissions

To configure the bot’s permissions:

1. Right-click your server name and select “Server Settings”
2. Navigate to the “Roles” section
3. Click on the bot’s role (usually named “BetaHub”)
4. Enable the required permissions based on your needs:

Basic Requirements (Always Needed)

• Embed Links - Required for all bot functionality
• Send Messages - Required for basic communication
• View Channels - Required to see and operate in channels

Sentiment Analysis Permissions

If you enable the sentiment analysis feature, the bot needs the View Channel permission for all channels that you want to monitor. If any of the channels are not visible to the bot, it will attempt to send you a DM to inform you about the issue.

Troubleshooting Permissions

If you encounter issues:

1. Bot Not Responding: Verify basic permissions (Send Messages, View Channels)
2. Can’t Create Threads: Check thread-related permissions
3. Can’t Post Announcements: Verify announcement channel permissions

Best Practices

• Run /info after adding the bot to verify permissions
• Check permissions before enabling new features
• Use role hierarchy to manage bot permissions effectively
• Keep bot permissions minimal for security
• Test features in a private channel first

Configuration

By default, the bot will react to /report command from any channel. This will trigger the bot to pop up a dialog box for the user to fill in the bug report details. The bot will then post the bug report in the designated bug report channel.

Make sure that your discord users have the permissions to execute slash commands. You can test it by typing / in the chat and see if the bot responds with a list of commands.

Bug Reporting

There are serveral ways to report a bug:

1. Using the /report command.
2. By mentioning the bot and providing a bug report in the same message.
3. By using the AI to identify the bug report in the conversation.
4. By pressing the Report a Bug button that can be pinned to the channel.

With the /report Command

The /report command will trigger a dialog box for the user to fill in the bug report details. The bot will then post the bug report in the designated bug report channel.

Device Info Field

Default: off

Configure whether and how the device info field appears in the /report dialog:

• optional: Shows the device info field, but users can leave it empty.
• loose: Requires users to fill in the field, but doesn’t validate the format.
• strict: Requires users to fill in the field with valid device information. If parsing fails, the user will be asked to retry.
• off: Doesn’t show the device info field in the dialog.

Minimum Description Length

Default: 70

Set the minimum number of characters required for the bug description in the /report dialog. This helps ensure that bug reports contain enough information to be actionable.

Listen Mode

Default: Disabled

When enabled, the bot will listen for all, bug reports only, support requests only or off. The bot will still respond to the /report command, but it will also listen for messages using Claude’s AI to identify bug reports and support-related messages.

To select the bugs channel, please execute the following command:

The bugs channel automatically becomes also the support channel. To add support-only channels, please execute the following command:

Listen Mode Notification Method

Default: public

This setting controls how the bot notifies users when their message has been classified as a bug report in listen mode:

• public: The bot replies directly in the channel where the message was posted, visible to everyone.
• dm: The bot attempts to send a direct message to the user. Note that this may fail if the user has DMs disabled.
• dm_with_fallback: The bot attempts to send a direct message first. If that fails, it will fall back to the bugs notification channel (if configured) or public notification.
• channel: The bot posts a notification in the bugs notification channel (requires bugs_notifications_channel to be set) and mentions the reporter.

Bug Notifications Channel

Default: Disabled

When set, the bot will post bug report notifications in the specified channel. This is particularly useful when using the channel notification method or dm_with_fallback when DMs fail.

Thread Mode

Default: Disabled

When enabled, the bot will create a new thread for each bug report. This will allow users to upload additional files and communicate with the bot without cluttering the main channel. Any notifications or messages from the bot will be sent directly to the user’s thread, if these are related to a specific bug report.

Thread Participants

Default: Empty

Configure which users should be automatically added as participants to threads created by the bot. This ensures key team members are always included in discussions related to bug reports or other threaded notifications.

Available commands for managing thread participants:

Add Users:

Adds one or more users to the thread participants list.

Remove Users:

Removes specified users from the thread participants list.

Set Complete List:

Replaces the entire thread participants list with the specified users.

List Participants:

Lists all current thread participants.

Clear Participants:

Removes all users from the thread participants list.

The Releases Channel

Default: Disabled

When enabled, the bot will post new releases announcements in the selected channel. The bot will notify everyone about the new release and attach the release notes to the message. You can create a new release from your BetaHub project’s page. Editing any release will automatically update the message in the Discord channel as well.

The Welcome Channel

Default: Disabled

When enabled, the bot will send a welcome message to the selected channel. The message will contain a link to the project’s page on BetaHub.

Ignored Users

Default: Empty

Configure which users should be ignored by the bot when detecting bugs and sentiments. This is useful for excluding bot accounts or users who frequently discuss technical issues without actually reporting bugs.

Available commands for managing ignored users:

Add Users:

Adds one or more users to the ignored users list.

Remove Users:

Removes specified users from the ignored users list.

List Ignored Users:

Lists all currently ignored users.

Clear Ignored Users:

Removes all users from the ignored users list.

Integrations

Blox.link

BetaHub bot integrates with Blox.link to automatically capture user’s Roblox username and ID as the user reports a bug from your Discord server.

Requirements

1. You must have a Blox.link account.
2. You must have the BetaHub Discord Bot installed in your Discord server.

Setup

To enable blox.link integration, you need to setup Blox.link server key with BetaHub bot.

1. Navigate to Blox.link Developer Dashboard and create a new server key.
2. Copy the server key.
3. Navigate to your Discord server and execute the following command:

The bot will respond with a message indicating that the integration is enabled. You can also check the integration status by using /info command.

AI-Driven Bug Submissions

How the AI Operates

Upon submission, the AI scrutinizes the bug report, assigning it a relevant subject and priority. It tags the report appropriately and searches for similar existing reports within the project. If a match is found, the new report is marked as a duplicate, raising the original report’s Heat value. This mechanism ensures testers don’t feel disheartened by repetitive reports, while developers gain a clearer picture of the bug’s prevalence.

Customizing AI Settings

Tailor your project’s bug submission verification in the ‘Settings / General’ section. Choose the Bug Description Validation Level:

• AI Check - The AI evaluates the report and alerts the user if the description is invalid or incomplete.
• Minimum Character Limit - Ensures the description is at least 50 characters long.
• No Check - Omits the validation process.

Multimedia Submission and Annotation

Users can attach and mark up multimedia files within their bug reports, providing developers with a clear depiction of the issues. This interactive feature allows users to convey bugs more precisely.

Supported Formats

• Screenshots - PNG, JPG, JPEG
• Videos - MP4, MOV, WEBM, AVI, FLV, WMV, MKV, MPG, MPEG, M4V, 3GP, 3G2
• Log files - TXT, LOG

Support Knowledge Base

BetaHub supports a support knowledge base that allows you to create a knowledge base for your project. This is useful for providing support to your users through the Discord bot whenever they try to report a bug that is already known, or for enablng the bot to jump in in the middle of the conversation with a solution to a problem that is being discussed. This allows to provide a better support to your users and to reduce the load on the developers.

Enabling the Knowledge Base

To enable the knowledge base, you need to go to the ‘Settings / General’ section and enable the ‘Support Knowledge’ option.

Then, you will notice a new ‘Knowledge Base’ menu item in the left-side menu.

Creating a Knowledge Base

To create a knowledge base, you need to go to the ‘Knowledge Base’ menu item and click on the ‘Upload New Document’ button.

From there, you will be able to either choose to upload a a PDF, TXT or MD file, or to paste the content of the document directly into the text area.

When uploaded, it will take just a moment for the document to be processed and made available for use.

Using bugs comments to create a knowledge base

You can use existing bug reports comments to create a knowledge base article. By clicking on the green tick button, the comment will be marked as a solution to the bug report and be submited along with the rest of the bug report to the knowledge base. This way, if someone else reports the same bug, the bot will be able to use the existing knowledge base article to provide a solution instead of creating a new one.

Testing the Knowledge Base

You can test the knowledge base by going to the ‘Knowledge Base’ menu item and using the Support Knowledge API testing feature. You can test three API’s for easier debugging:

• Search API - To see what results has been returned for a given query.
• Context Retrieval API - To see what context has been built for LLM to use.
• Ask API - To see what answer a user would get if they asked a question.

Using the Knowledge Base

When the knowledge base is enabled, the bot will use it to provide a response to the user’s message.

Enabling the Discord Bot to use the Knowledge Base

As soon as your project has the knowledge base enabled, the bot will be able to use it to see if there’s a solution to the user’s problem, but will do that only if the user will use the /report command or click on the Report a Bug button.

Yet, the bot can also be configured to use the knowledge base to answer questions in the Discord server without the user having to report a bug. This mode is called the ‘Listen Mode’ and it can be enabled in the bot settings. The bot can listen on the same channels as the bug reporting, or on a different set of channels. For more information, check the Listen Mode section.

Game Facts

BetaHub’s Game Facts feature enhances AI understanding of bug reports through detailed contextual awareness of your game. This ensures more accurate bug report processing, categorization, and prioritization.

How It Works

The Game Facts system allows developers to define crucial information about their game, which the AI uses to better understand bug reports and user feedback. This includes:

• Game name, genre, and key features
• Critical vs. non-critical functionalities
• Glossary of in-game terminology (items, enemies, mechanics)
• Game-specific priority rules

This contextual information helps the AI:

• Generate more precise bug titles and descriptions
• Assign appropriate tags and priorities based on game-specific importance
• Better understand game-specific terminology in bug reports

Quick Setup

1. Navigate to your project page on BetaHub
2. Select ‘Game Facts’ from the left-hand menu
3. Either:
   • Fill out the Game Facts form manually
   • Use the AI-assisted setup by pasting your game documentation

AI-Assisted Configuration

To use the AI-assisted setup:

1. Prepare any text containing information about your game (documentation, store page, etc.)
2. Click the “Upload the Document” button in the Game Facts section
3. Paste your text into the provided field and click the “Extract Information” button
4. Review and edit the automatically extracted information

The AI will analyze your text and populate the form with relevant information about your game, saving you time in the setup process.

Issues Tags Configuration

BetaHub allows you to define custom tags for categorizing issues in your project. These tags are essential for organizing bug reports and can be automatically assigned by the AI.

Default Tags

Every new project comes with predefined tags covering common bug categories in games. These default tags provide a solid foundation for bug categorization right from the start. You can customize these tags or add new ones based on your specific needs.

Tag Structure

BetaHub supports a hierarchical tag system with main tags and sub-tags:

• Main Tags: Represent broad categories (e.g., Performance, Graphics, Network)
• Sub-Tags: Provide specific details within main categories (e.g., under Performance: Crash, Freeze, FPS Drop)

Multiple tags can be assigned to a single bug report, allowing for more precise categorization.

Setting Up Tags

1. Navigate to your project on BetaHub
2. Select ‘Issues Tags’ from the left-hand menu
3. Create or modify tags by specifying:
   • Name (spaces are allowed, e.g., “FPS Drop”)
   • Description
   • Color
   • Parent tag (if it’s a sub-tag)

AI Tag Assignment

The AI automatically assigns appropriate tags to new bug reports based on their content. For optimal AI tagging:

• Write clear, specific tag descriptions
• Ensure tags don’t overlap in meaning
• Create comprehensive coverage of possible issue types
• Use the hierarchical structure effectively

Best Practices

• Use descriptive, readable names for tags
• Create a logical hierarchy of main tags and sub-tags
• Review and refine tags periodically based on actual usage
• Consider creating tags for:
  • Issue types (crash, performance, visual)
  • Game systems (inventory, combat, networking)
  • Severity levels (if not using built-in priority system)

Issues Auto-Archiving

BetaHub allows you to automatically archive issues after a certain period of time. This is useful to keep the project clean and to avoid cluttering the issues list with old issues that are no longer relevant. Archived issues are flagged with the ‘Archived’ label and can be still seen on the issues list by setting the ‘Archive Status’ filter to ‘Archived’ or ‘All’.

Enabling the Auto-Archiving

To enable the auto-archiving, you need to go to the ‘Settings / General’ section and enable the ‘Issues Auto-Archive’ option.

Sentiment Analysis

BetaHub’s AI employs sentiment analysis to gauge your Discord’s community mood. This feature is particularly useful for identifying potential issues before they escalate. The AI will notify you if it detects a negative sentiment, allowing you to address the situation promptly.

Enabling Sentiment Analysis

To activate sentiment analysis, you must invite BetaHub Discord Bot to your server. Then, use the /info command and press the Configure Sentiments Channels button. Select the channels you wish to monitor, and the bot will begin analyzing the sentiment of the messages within those channels.

Sentiments Dashboard

You can access the sentiment analysis dashboard from the BetaHub project page by finding the Sentiments navigation item on the left-side menu. The dashboard displays the sentiment analysis results for the selected (all by default) channels, allowing you to monitor the community’s mood.

The sentiment dashboard consists of the following elements:

• Rating: The most recent sentiments rating from 0 to 5. The higher the rating, the more positive the sentiment.
• Records: The number of records analyzed in the selected period. The more records, the more accurate the sentiment analysis.
• Frequency: The frequency of reports per day.
• Categories: The sentiment categories, including:
  • Excited
  • Positive
  • Neutral
  • Negative
  • Frustrated
  • Toxic
• Top Words: The most frequently used words in the selected period. The words are color-coded based on their sentiment category. The number in the parentheses indicates the word’s frequency.
• Trend Chart: The detailed sentiment trend chart for the selected period. The chart displays the sentiment rating and the number of records analyzed per day.

Filtering and Navigation

You can filter the sentiment analysis results by date range, sentiment category, channels and words.

• Filtering by Date: Select the date range to analyze the sentiment for the specified period.
• Filtering by Channel: Choose the channels to analyze the sentiment. You can select multiple channels. Selecting none will analyze all channels.
• Filtering by Words: You can click on the words in the Top Words section to filter the sentiment analysis results by the selected word.
• Filtering by Category: Click on the sentiment category on the Categories bar chart to filter the sentiment analysis results by the selected category.

Troubleshooting Sentiments

The bot is not responding to commands

Ensure the bot has the necessary permissions to execute slash commands and if you finished the setup procedure correctly.

I don’t see the sentiment analysis results

Make sure your bot is configured to receive sentiments by using the /info command and pressing the Configure Sentiments Channels button. The sentiment dashboard refreshes every 5-10 minutes, so you might need to wait a bit.

Still need help?

If you’re experiencing issues with sentiment analysis, please join our Discord server and ask for help in the #support channel.

Notifications

Manage your notification preferences through your profile page, where you can set up email and Discord notifications for different types of events.

Developer Notifications

By default, BetaHub notifies you about:

• New bug reports
• New feature requests
• New releases
• New assignments

To receive notifications about other activities on these items (like comments or status changes), you need to Watch the specific item by clicking the Watch button on its page.

You can modify these default notification settings in Settings / General under Notification Settings:

• Do not notify: Receive notifications only when directly mentioned in comments
• Instant notifications: Get immediate notifications for new bugs, features, and releases
• Instant notifications and watch: Get immediate notifications and automatically watch new items to receive updates about all activity

Tester Notifications

As a project member, you’ll receive notifications about:

• New releases
• Updates to bug reports you’re involved with
• Updates to feature requests you’re involved with

To stop receiving notifications for a specific item, either:

• Click the Unwatch button on the item’s page
• Leave the project entirely