Menu

Quick Reference

Lookup tables for statuses, file formats, and technical specifications.

Looking for feature explanations? See Features Overview →

On This Page

Bug Report Statuses

These are the default built-in statuses for every project:

Status Description
Hidden Draft state, not visible to the team
Open Just submitted, awaiting triage
In Progress Being actively worked on
Needs More Info Awaiting details from the reporter
Resolved Fixed, ready for verification
Closed Verified as working
Won’t Fix Declined by the team
Duplicate Linked to an existing report
Pending Moderation Awaiting review (moderated projects only)

You can rename these statuses and create custom ones to match your workflow. For example, rename “Won’t Fix” to “By Design” or add stages like “In Review” or “QA Verified”.

Configure Issue Statuses →

Suggestion Statuses

Status Description
Open Newly submitted
Under Review Being evaluated by the team
Planned Accepted for future implementation
Started Currently being worked on
Completed Fully implemented
Declined Not accepted (with optional reason)

Heat Scoring

Heat is a dynamic score that helps prioritize bugs based on community impact. Higher Heat = more urgent.

What increases Heat:

  • Duplicates – Each duplicate report adds to the original’s Heat
  • Watchers – Issues that resonate with users gain watchers, naturally rising in visibility
  • Recency – Recent activity boosts Heat
  • Priority – Higher priority issues have higher base Heat

Why it matters:

  • Testers aren’t discouraged from reporting duplicates (they’re valuable signals)
  • Popular issues naturally rise to the top
  • Developers can sort by Heat to find the most impactful bugs

Learn more about using Heat for prioritization.

Duplicate Detection

The AI automatically identifies similar bug reports:

  1. When a bug is submitted, the AI analyzes the description
  2. It searches existing reports for similar issues
  3. If a match is found, the new report is marked as a duplicate
  4. The original report’s Heat increases

Duplicates remain visible and linked, so reporters can track the original issue’s progress.

Priority Levels

The AI assigns priority based on:

Factor Example
Severity keywords “crash”, “data loss”, “unplayable” → higher priority
Game Facts context Issues in critical systems get priority
Impact scope Affects all players vs. edge case
Crash indicators Stack traces, error codes

Priority can be manually adjusted after submission.

AI Validation Levels

Control how strictly the AI validates bug descriptions:

Level Behavior
0 - No Check Accepts any description
1 - Character Limit Requires minimum length
2 - Loose AI Check Flags issues but allows submission
3 - Strict AI Check Rejects insufficient descriptions

Configure in Project Settings → Bug Handling.

File Format Reference

Supported Formats

Type Formats Max Size
Screenshots PNG, JPG, JPEG 10 MB
Videos MP4, MOV, WEBM, AVI 500 MB
Log files TXT, LOG 50 MB

Video Recording Duration

Video recording duration depends on your plan:

Plan Duration
Basic 60 seconds
Standard 5 minutes
Pro 30 minutes
Enterprise 60 minutes

Search and Filtering

Find issues quickly with:

  • Full-text search – Searches titles, descriptions, and comments
  • Status filter – Show only Open, In Progress, etc.
  • Priority filter – Filter by priority level
  • Tag filter – Filter by assigned tags
  • Assignee filter – Show issues assigned to specific people
  • Date range – Filter by creation or update date
  • Heat sort – Sort by community impact

Webhooks Events

BetaHub can notify external systems when events occur:

Event Trigger
issue_created New bug report submitted
issue_status_changed Bug status updated
feature_request_created New suggestion submitted
ticket_created New support ticket submitted

Configure webhooks in Integrations → Webhooks.

See Also

Quick Reference

Lookup tables for statuses, file formats, and technical specifications.

Looking for feature explanations? See Features Overview →

On This Page

Bug Report Statuses

These are the default built-in statuses for every project:

Status Description
Hidden Draft state, not visible to the team
Open Just submitted, awaiting triage
In Progress Being actively worked on
Needs More Info Awaiting details from the reporter
Resolved Fixed, ready for verification
Closed Verified as working
Won’t Fix Declined by the team
Duplicate Linked to an existing report
Pending Moderation Awaiting review (moderated projects only)

You can rename these statuses and create custom ones to match your workflow. For example, rename “Won’t Fix” to “By Design” or add stages like “In Review” or “QA Verified”.

Configure Issue Statuses →

Suggestion Statuses

Status Description
Open Newly submitted
Under Review Being evaluated by the team
Planned Accepted for future implementation
Started Currently being worked on
Completed Fully implemented
Declined Not accepted (with optional reason)

Heat Scoring

Heat is a dynamic score that helps prioritize bugs based on community impact. Higher Heat = more urgent.

What increases Heat:

  • Duplicates – Each duplicate report adds to the original’s Heat
  • Watchers – Issues that resonate with users gain watchers, naturally rising in visibility
  • Recency – Recent activity boosts Heat
  • Priority – Higher priority issues have higher base Heat

Why it matters:

  • Testers aren’t discouraged from reporting duplicates (they’re valuable signals)
  • Popular issues naturally rise to the top
  • Developers can sort by Heat to find the most impactful bugs

Learn more about using Heat for prioritization.

Duplicate Detection

The AI automatically identifies similar bug reports:

  1. When a bug is submitted, the AI analyzes the description
  2. It searches existing reports for similar issues
  3. If a match is found, the new report is marked as a duplicate
  4. The original report’s Heat increases

Duplicates remain visible and linked, so reporters can track the original issue’s progress.

Priority Levels

The AI assigns priority based on:

Factor Example
Severity keywords “crash”, “data loss”, “unplayable” → higher priority
Game Facts context Issues in critical systems get priority
Impact scope Affects all players vs. edge case
Crash indicators Stack traces, error codes

Priority can be manually adjusted after submission.

AI Validation Levels

Control how strictly the AI validates bug descriptions:

Level Behavior
0 - No Check Accepts any description
1 - Character Limit Requires minimum length
2 - Loose AI Check Flags issues but allows submission
3 - Strict AI Check Rejects insufficient descriptions

Configure in Project Settings → Bug Handling.

File Format Reference

Supported Formats

Type Formats Max Size
Screenshots PNG, JPG, JPEG 10 MB
Videos MP4, MOV, WEBM, AVI 500 MB
Log files TXT, LOG 50 MB

Video Recording Duration

Video recording duration depends on your plan:

Plan Duration
Basic 60 seconds
Standard 5 minutes
Pro 30 minutes
Enterprise 60 minutes

Search and Filtering

Find issues quickly with:

  • Full-text search – Searches titles, descriptions, and comments
  • Status filter – Show only Open, In Progress, etc.
  • Priority filter – Filter by priority level
  • Tag filter – Filter by assigned tags
  • Assignee filter – Show issues assigned to specific people
  • Date range – Filter by creation or update date
  • Heat sort – Sort by community impact

Webhooks Events

BetaHub can notify external systems when events occur:

Event Trigger
issue_created New bug report submitted
issue_status_changed Bug status updated
feature_request_created New suggestion submitted
ticket_created New support ticket submitted

Configure webhooks in Integrations → Webhooks.

See Also

On This Page