Project Settings

Configure your BetaHub project to optimize game testing, feedback collection, and team collaboration. Project settings control everything from basic project information to advanced AI features and integrations.

Accessing Project Settings

To access your project settings:

1. Navigate to your project dashboard
2. Click Settings in the project sidebar
3. Choose the appropriate settings category

Permission Required: You must have Developer role or higher to access and modify project settings.

General Settings

The General settings page contains the core configuration options for your project.

Project Information

Project Name

• The display name for your project across BetaHub
• Visible to all project members and in public project listings
• Can be changed at any time without affecting functionality

Organization

• Associates your project with an organization for billing and team management
• Cannot be changed for existing projects from the settings page
• For new projects, select from available organizations or create a new one

Access Control

• Private: Project is invite-only and not listed publicly
• Public: Project appears in public listings and anyone can join
• Projects under review or rejected by moderators are automatically set to private

Content Settings

• Mature Content: Mark if your project contains mature themes
• Affects visibility and filtering in public project listings
• Required for appropriate content categorization

Banner

• Upload a banner image to represent your project
• Required for inclusion in the public projects list
• Supports standard image formats (JPG, PNG, etc.)

Description

• Detailed project description supporting Markdown formatting
• Displayed on your project’s main page and in search results
• Use this to explain your game’s concept, testing goals, and desired feedback

Social Media Links

• Add links to your social media profiles and community spaces
• Supports Twitter, Discord, YouTube, Twitch, Reddit, Steam, and more
• Helps players connect with your broader community

Platforms

• Select all platforms your game supports
• Affects device selection options when users report bugs
• Used for filtering and categorization

Bug Handling Settings

Bug Description Validation Level (0-3)

• Level 0: No validation - accepts any description length
• Level 1: Basic validation - requires minimum description length
• Level 2: Moderate validation - AI checks for basic detail requirements
• Level 3: Strict validation - AI ensures comprehensive bug descriptions
• Higher levels improve bug quality but may create barriers for some users

Bug Auto-Archive

• Automatically archives bugs that haven’t been updated for a specified number of days
• Archived bugs don’t appear in default views but remain accessible
• Helps keep your active bug list manageable
• Set archive threshold between 1-365 days

Bug Description Display

• Show AI summary, collapse original: Displays AI-generated summaries prominently
• Show both AI summary and original: Shows all content expanded
• Show original description only: Hides AI-generated content
• Particularly relevant for bugs imported from Discord or other integrations

Bug Title Generation Language

• Choose the language for AI-generated bug titles
• “Same as Description” adapts to the reporter’s language
• Consistent language options help maintain organized bug lists

Required Fields

• Require device information: Forces users to select a device when reporting bugs
• Helps with reproduction and prioritization
• Does not affect Discord bot submissions

Ticket Settings

Ticket Auto-Close

• Automatically closes tickets awaiting feedback after specified days
• Prevents tickets from staying in limbo indefinitely
• System adds explanatory comment when auto-closing
• Set threshold between 1-365 days

Tester Permissions

Bug Isolation

• When enabled, each tester can only see bugs they’ve reported themselves
• Useful for competitive testing or when privacy is important
• Overrides all other visibility settings when active

Commenting Permissions

• Allow Testers to Comment on All Bugs: Testers can comment on any accessible bug
• Restrict to Own Bugs: Testers can only comment on bugs they reported
• Affects community interaction and collaboration

Tester Media Visibility These settings control what testers can see from other testers’ bug reports:

• Screenshots: Allow viewing of screenshot attachments
• Videos: Allow viewing of video attachments
• Log Files: Allow viewing of log file attachments
• Device Information: Allow viewing of device details
• All settings are ignored when “Bug Isolation” is enabled
• Testers always see full content of their own bug reports

Features & Modules

Enable or disable core functionality for your project:

Available Modules:

• Bugs: Core issue tracking functionality
• Suggestions: Feature request collection and voting
• Sentiments: AI-powered sentiment analysis of feedback
• Tickets: Support ticket system for user assistance

Experimental Features

Cutting-edge features that may be unstable or incomplete:

Automation Tasks

• Enables Discord bot to request additional media/logs automatically
• Allows drag-and-drop media sharing in Discord without web login
• Makes bug reporting more intuitive for Discord users

Support Knowledge

• Enables bot responses to known bugs and common questions
• Reduces repetitive support workload
• Requires setup of knowledge base content

Keys Distribution

• Enables game key distribution to testers
• Supports automated key delivery and tracking
• Useful for closed beta testing

Playtesting

• Enables gameplay video upload and review system
• Allows developers to review tester gameplay sessions
• Supports structured playtesting workflows

Suggestion Settings

Split Behavior

• Automatic: AI automatically splits complex suggestions into separate items
• Manual Review: AI identifies splittable suggestions but waits for developer approval
• Manual review provides more control but requires additional developer time

Notification Settings

Configure how you receive notifications for this specific project:

• Instant Notifications: Immediate alerts for all activity
• Daily Digest: Summary email once per day
• Weekly Digest: Summary email once per week
• Disabled: No notifications for this project

Default Table Columns

Configure which columns appear by default in your project’s issues table:

• Users can still customize their individual view
• Affects the initial view for new users and guests
• Common columns include status, priority, tags, device, and assignment

Game Facts

Game Facts provide detailed information about your game to improve AI-powered features like bug categorization and duplicate detection.

Core Information

Description: Comprehensive overview of your game’s concept, mechanics, and goals Genre: Primary and secondary genres that best describe your game Target Audience: Age ranges and player types you’re targeting Platforms: Detailed platform support including version requirements

Core Mechanics

Key Features: List the most important gameplay elements Game Modes: Single-player, multiplayer, cooperative, etc. Controls: Platform-specific control schemes and input methods

Technical Specifications

Supported Platforms: Detailed platform compatibility Minimum System Requirements: Hardware and software requirements Performance Considerations: Known performance characteristics or limitations

Game Progression

Level Design: How levels or areas are structured Progression System: Character advancement, unlocks, achievements

Bug Reporting Guidelines

Critical Components: Game systems that are most important to test Non-Critical Components: Systems that are less critical for core experience Known Bugs: Currently known issues to help identify duplicates

Glossary

Define game-specific terms in categories:

• Items: In-game objects, tools, weapons, etc.
• Characters: NPCs, player characters, enemies
• Events: Quests, missions, special occurrences
• Locations: Areas, levels, maps
• Other Terms: Any other game-specific vocabulary

Discord Bot Integration

The Discord bot integration allows automatic bug collection and community engagement directly from your Discord server.

Setup Process

Step 1: Invite the Bot

• Click the “Invite the Bot” link to add BetaHub bot to your Discord server
• Ensure you have “Manage Server” permissions in Discord
• If bot is already installed elsewhere, the previous installation will be disconnected

Step 2: Associate with Project

In the Discord channel where you want the bot active, use the /set command to associate it with your BetaHub project:

/set project YOUR_PROJECT_SECRET

Your project’s Discord secret can be found in Settings > Discord Bot Integration on your project page. Look for the “Project Secret” field (example: abc123def456ghi789).

Example command:

/set project abc123def456ghi789

The bot will reply: “✅ Project associated successfully! Use /info to verify configuration.”

Step 3: Configure Permissions

• Ensure your @everyone role or tester role has “Use Application Commands” permission
• This allows community members to use slash commands

Bot Features

Bug Reporting

• Users can report bugs with /report command
• Bot guides users through description process
• Automatically creates issues in your BetaHub project
• Provides links back to the web interface

Release Notifications

• Automatically posts release notes when you publish new versions
• Includes download links for easy access
• Mentions bug reporters who contributed to the release
• Configure with /set releases_channel true

Welcome Messages

• Greets new server members with project information
• Provides instructions for bug reporting and community participation
• Configure with /set welcome_channel true

Automatic Bug Collection

• Monitors #bugs channel (or similar) for messages
• Converts messages to bug reports automatically
• Works with channels named #bug-reports, #issues, etc.
• Configure specific channel with /set bugs_channel #channel-name

Configuration Commands

• /info: Check bot status and configuration
• /set project [secret]: Associate bot with your project
• /set releases_channel true/false: Enable/disable release notifications
• /set welcome_channel true/false: Enable/disable welcome messages
• /set bugs_channel #channel-name: Set specific bugs collection channel
• /set bugs_channel false: Disable automatic bug collection
• /set threads_channel #channel-name: Specify channel for thread creation when thread mode is enabled

Tags Management

Tags help categorize and organize bugs and suggestions for better tracking and filtering.

Bug Tags vs Suggestion Tags

• Bug Tags: Used for categorizing issues, crashes, and problems
• Suggestion Tags: Used for categorizing feature requests and improvements
• Each type has its own management interface but similar functionality

Creating and Managing Tags

Creating Tags:

1. Navigate to Settings > Tags in your project
2. Choose either Bug Tags or Suggestion Tags tab
3. Click Add Tag button
4. Enter tag name and select a color
5. (Optional) Add a description to help team members understand when to use the tag
6. (Optional) To create a child tag, select a parent tag first, then click the + icon next to it
7. Click Save

Editing or Deleting Tags:

• Click the ⋮ menu next to any tag
• Select Edit to change name, color, or description
• Select Delete to remove the tag (this will remove it from all existing reports)

Tag Hierarchy:

• Tags can have parent-child relationships for better organization
• Useful for creating categories like “UI” with subtags “UI - Menu”, “UI - HUD”
• Helps with filtering and organization

Best Practices:

• Start with broad categories, add specific tags as needed
• Use clear, consistent naming conventions
• Regularly review and consolidate similar tags
• Train team members on proper tag usage

Custom Fields

Custom fields allow you to collect additional structured information beyond standard fields for Issues (bugs), Suggestions (feature requests), and Support Tickets. This flexibility enables you to gather project-specific data that matters most to your development workflow.

Overview

Custom fields work across all three entity types:

• Issues (Bugs): Capture technical reproduction details, affected game systems, or crash conditions
• Suggestions: Collect implementation complexity, feature area, or business value assessments
• Support Tickets: Gather customer priority, product versions, or support categories

Each entity type can have its own set of custom fields with independent configurations.

Field Types

BetaHub supports four field types to match different data collection needs:

Text Field

• Free-form text input for detailed information
• Best for: descriptions, comments, version numbers, or any textual data
• Example uses: “Steps to Reproduce”, “Expected Behavior”, “Player Level”

Boolean (Checkbox)

• Simple yes/no selection
• Best for: binary choices or feature flags
• Example uses: “Can Reproduce Consistently”, “Affects Multiplayer”, “Critical for Release”

Single Select (Dropdown)

• Choose one option from a predefined list
• Best for: mutually exclusive categories
• Example uses: “Affected Game System” (Combat, UI, Audio, etc.), “Platform”, “Priority Level”

Multi Select (Multiple Checkboxes)

• Choose multiple options from a predefined list
• Best for: scenarios where multiple categories apply
• Example uses: “Affected Features”, “Related Systems”, “Tags”

Visibility and Access Control

Control who can see and edit custom fields:

Player-Settable Fields

• When enabled, players can fill these fields when submitting reports
• Shows in submission forms for bugs, suggestions, or tickets
• Useful for gathering information players have (like device, settings, or preferences)

Developer-Only Fields

• When disabled, only developers can see and edit these fields
• Hidden from player submission forms
• Perfect for internal tracking (priority, sprint assignment, technical notes)

Player-Viewable Fields

• Controls whether players can view field values after submission
• Useful for showing status or classification back to reporters
• Can be hidden to keep internal categorization private

When to Use Custom Fields

For Game Development:

• Capture which game systems are affected (Combat, UI, Inventory, etc.)
• Track platform-specific issues (Mobile vs Desktop, specific OS versions)
• Collect player progression context (Level reached, items owned, quest status)
• Assess business impact (Blocks release, Affects monetization)

For Support Tickets:

• Categorize support request types
• Track customer priority levels
• Collect product version information
• Monitor resolution status

For Feature Requests:

• Estimate implementation effort
• Track which roadmap category requests fit into
• Gauge user impact or request urgency
• Link to related design documents

Setting Up Custom Fields

1. Navigate to Settings > Custom Fields in your project
2. Click New Custom Field
3. Choose which entity type this field applies to (Issue, Suggestion, or Ticket)
4. Enter a clear field name (e.g., “Affected Game System”)
5. Select the field type that matches your data
6. For select fields, add your options (one per line)
7. Configure visibility:
   • Check “Required” if this field must be filled (requires player-settable)
   • Check “Player Settable” to show in submission forms
   • Check “Player Viewable” to show field values to reporters
8. Save the field

Field Identifiers for Integrations

When you create a custom field, BetaHub automatically generates a unique identifier that can be used in integration dynamic expressions. These identifiers make your integration templates readable and stable.

How It Works:

Each custom field gets an identifier automatically generated from its name. The identifier is a code-safe slug: lowercase, with spaces replaced by underscores and special characters removed.

Examples:

• “Platform” becomes platform
• “User Experience Rating” becomes user_experience_rating
• “Player’s Feedback” becomes player_s_feedback

Why This Matters:

Identifiers provide stability for your integrations:

• Stable: Renaming the field display name won’t break your integration templates
• Predictable: Field names are automatically converted to valid identifiers

Viewing Identifiers:

The identifier appears in the custom fields list with a code format (e.g., platform). Hover over the “Identifier” column header to see a tooltip explaining how to use identifiers in integrations.

Editing Identifiers:

To edit an identifier:

1. Edit the custom field
2. Check the box: “Allow editing identifier”
3. Modify the identifier value
4. Read the warning carefully
5. Save the field

Using Identifiers in Integrations:

Reference custom fields in dynamic expressions with the format custom_field_{identifier}:

Bug: {{{ title }}}
Platform: {{{ custom_field_platform }}}
Experience Rating: {{{ custom_field_user_experience_rating }}}

See the Dynamic Expression Examples for complete integration templates.

Flexible Data Handling

Custom fields support two data storage formats:

Name-Based Format (Recommended for most cases)

• Store field values by field name
• More flexible if you rename or restructure fields
• Example: {"Platform": "PC", "Game System": "Combat"}

ID-Based Format (For API integrations)

• Store field values by field ID
• More stable for programmatic access
• Example: {"field_123": "PC", "field_456": "Combat"}

Undefined Fields (Advanced)

• Fields can be stored without corresponding field definitions
• Hidden from players, visible to developers with raw access
• Useful for temporary data or migration scenarios

Best Practices

Field Design:

• Use clear, self-explanatory field names
• Keep option lists concise (5-10 options ideal)
• Make fields optional unless truly necessary
• Consider player burden when adding fields

Organization:

• Group related fields by entity type
• Use consistent naming conventions across fields
• Review and consolidate similar fields regularly
• Update field options as your project evolves

Player Experience:

• Don’t overwhelm players with too many required fields
• Use player-settable fields sparingly for bugs (players want quick reporting)
• Suggestions can handle more fields since they’re less time-sensitive
• Provide helpful field labels that explain what information you need

Developer Workflow:

• Use developer-only fields for internal prioritization and triage
• Consider using multi-select for flexible categorization
• Boolean fields work well for quick filtering and sorting
• Text fields are good for additional context but harder to filter

Examples

Bug Report Custom Fields:

Field: "Affected Game System"
Type: Single Select
Options: Combat, UI, Audio, Multiplayer, Save System
Player Settable: Yes
Player Viewable: Yes
Required: No

Field: "Blocks Release"
Type: Boolean
Player Settable: No (Developer Only)
Player Viewable: No
Required: No

Suggestion Custom Fields:

Field: "Feature Category"
Type: Single Select
Options: Gameplay, UI/UX, Content, Performance, Social
Player Settable: Yes
Player Viewable: Yes
Required: Yes

Field: "Implementation Complexity"
Type: Single Select
Options: Small, Medium, Large, Extra Large
Player Settable: No (Developer Only)
Player Viewable: Yes
Required: No

Team Invitations

Manage who has access to your project and at what permission level.

Generating Invitation Links

1. Navigate to your project dashboard
2. Click Team in the project sidebar
3. Click Generate Invitation button
4. Select the role for invited members (Developer, Tester, or Viewer)
5. Copy the generated URL
6. Share with team members via email or messaging

The invitation link will look like: https://betahub.io/invite/abc123...

Managing Invitations

To track usage:

• Go to Team > Invitations to see which links have been used
• View who accepted each invitation and when

To revoke unused invitations:

• In Team > Invitations, click the ⋮ menu next to the invitation
• Select Revoke to deactivate the link

Role-Based Access

Different roles have different capabilities:

• Developer: Full project access and settings management
• Tester: Can report bugs and view permitted content based on project settings
• Viewer: Read-only access to permitted content

External Integrations

Connect your BetaHub project with external tools for streamlined workflow management.

Available Integrations

All integrations require an organization with the integrations feature enabled:

Jira

• Sync bugs to Jira issues for development tracking
• Bidirectional updates between platforms
• Customizable field mapping

Asana

• Create Asana tasks from bug reports
• Track development progress
• Team collaboration features

GitHub

• Link bugs to GitHub issues
• Connect to repository management workflow
• Support for GitHub issue templates

Monday.com

• Project management integration
• Custom workflow support
• Team collaboration features

Notion

• Documentation and knowledge base integration
• Custom database support
• Team wiki features

Redmine

• Open-source project management integration
• Issue tracking and time management
• Custom field support

Integration Setup

1. Ensure your organization has the integrations feature enabled
2. Navigate to the Integrations settings page
3. Select the integration you want to configure
4. Follow the authentication and setup process
5. Configure field mapping and sync preferences
6. Test the integration with a sample bug report

Best Practices

Getting Started

1. Start Simple: Configure basic project information first
2. Test Discord Bot: Set up bot integration early if using Discord
3. Define Tags: Create initial tag structure before collecting many reports
4. Set Permissions: Configure tester permissions based on your privacy needs
5. Enable Notifications: Set up appropriate notification levels for your team

Ongoing Management

1. Regular Review: Periodically review and update settings as your project evolves
2. Monitor Usage: Check which features are being used and adjust accordingly
3. Team Training: Ensure team members understand the settings and their impact
4. Feedback Loop: Ask testers about their experience and adjust settings to improve it

Advanced Configuration

1. AI Features: Use Game Facts to improve AI accuracy
2. Integrations: Set up external tool integrations for streamlined workflow
3. Custom Fields: Add project-specific data collection
4. Automation: Use experimental features to reduce manual work

Common Pitfalls to Avoid

1. Over-restricting Testers: Too many restrictions can discourage participation
2. Ignoring Notifications: Missing important updates due to poor notification settings
3. Inconsistent Tags: Poor tag management leads to disorganized reports
4. Skipping Game Facts: Missing opportunities for better AI assistance
5. Not Testing Settings: Failing to verify settings work as expected

Troubleshooting

Discord Bot Issues

• Verify bot has proper permissions in Discord
• Check that project association command was run correctly
• Ensure channel permissions allow bot to read messages
• Use /info command to verify bot status

Integration Problems

• Confirm organization has integrations feature enabled
• Verify authentication tokens are current
• Check field mapping configuration
• Test with simple bug reports first

Notification Issues

• Check both personal and project notification settings
• Verify email address is confirmed
• Look for notifications in spam/promotions folders
• Test with low-volume settings first

Permission Confusion

• Review role assignments for team members
• Understand difference between project and organization permissions
• Check tester visibility settings if users can’t see expected content
• Verify invitation links are for correct roles

Next Steps

After configuring your project settings:

• Integrations - Connect your project with external tools
• API Access - Set up API access for programmatic integration