Menu

Public Bug Board

Share a live, read-only view of your project’s bugs with players and community members. The Public Bug Board gives external visitors a link to browse reported bugs, check their status, and optionally leave comments — all without needing a BetaHub account to view.

This is useful when you want to:

  • Show players that reported bugs are being tracked
  • Let your community follow bug progress transparently
  • Reduce duplicate reports by making known issues visible

Enabling the Public Bug Board

  1. Open your project and go to the Bugs page
  2. Click Quick Actions in the top-right corner
  3. Select Enable Public Bug Board

Once enabled, a unique shareable URL is generated for your board. You can configure the board and copy the link from the Settings → Bugs page.

You can also access board settings through Quick Actions → Public Bug Board → Settings on the Bugs page.

Open the Settings → Bugs page — the shareable URL is displayed at the top of the Public Bug Board section. Click Copy to copy it to your clipboard.

Anyone with this link can view the board. No sign-in is required.

Tip: Share the link on your Discord server, Steam page, community forum, or anywhere your players gather.

Configuring the Board

The Settings → Bugs page lets you control exactly what visitors see on your public board.

Visible Columns

Choose which columns appear in the bug list table. Available columns include:

Column Description
Title Bug title (always shown)
Status Current status (e.g., Open, In Progress)
Priority Priority level
Heat Community interest indicator
Occurrence Number of times this bug has been reported
Created Date When the bug was first reported
Updated Date When the bug was last updated
Reported By Who reported the bug
Assigned To Who is working on it
Release Which release the bug is associated with
Duplicates Number of duplicate reports
Due Date When the bug is due
Ext. Links Links to external tracking systems

By default, the board shows: Title, Status, Priority, Heat, Created Date, and Occurrence.

Visible Statuses

Select which bug statuses appear on the board. By default, the board shows bugs with these statuses:

  • Open — New, unresolved bugs
  • In Progress — Bugs being actively worked on
  • Needs More Info — Bugs that need additional details

You can also enable:

  • Resolved — Bugs that have been fixed
  • Closed — Bugs that are no longer relevant
  • Won’t Fix — Bugs that won’t be addressed

When multiple statuses are visible, the board displays tabs so visitors can filter by status.

Sorting

Control the default sort order of the bug list:

  • Sort by: Heat (default), ID, Priority, Occurrence, Duplicates, Created Date, Updated Date, or Due Date
  • Direction: Descending (default) or Ascending

Display Limit

Set the maximum number of bugs shown on the board, from 1 to 100 (default: 25). This acts as a hard cap — only the top bugs (based on your sort order) will be visible, even if more bugs match the filters.

Commenting

When commenting is enabled, visitors can leave comments on individual bugs after signing in to BetaHub. When disabled, the board is completely read-only.

Commenting is off by default.

What Visitors See

Bug List

Visitors see a clean table of bugs with the columns you’ve configured. If multiple statuses are visible, tabs at the top let them filter by status. Clicking any bug row opens its detail page.

The project name is displayed at the top of the board. If your project is publicly accessible, the name links back to the project page.

Bug Detail Page

The detail page shows:

  • Bug title and status
  • Tags and labels (if any)
  • Description and steps to reproduce (if provided)
  • Screenshots (if attached) — developer-private media is automatically excluded
  • Metadata based on your visible column settings (priority, heat, reporter, etc.)
  • Comments section (if commenting is enabled)

Bug titles, descriptions, and steps to reproduce are filtered for profanity before being displayed, unless the project’s profanity filter has been disabled in Content Settings.

Disabling the Board

To disable the public bug board:

  1. Go to Quick Actions → Public Bug Board → Disable on the Bugs page, or click Disable Public Board on the Settings → Bugs page
  2. Confirm the action

Disabling the board immediately revokes the link. Anyone visiting the old URL will see a “Not Found” message. If you re-enable the board later, a new URL is generated — the old link will not work again.

See Also

Public Bug Board

Share a live, read-only view of your project’s bugs with players and community members. The Public Bug Board gives external visitors a link to browse reported bugs, check their status, and optionally leave comments — all without needing a BetaHub account to view.

This is useful when you want to:

  • Show players that reported bugs are being tracked
  • Let your community follow bug progress transparently
  • Reduce duplicate reports by making known issues visible

Enabling the Public Bug Board

  1. Open your project and go to the Bugs page
  2. Click Quick Actions in the top-right corner
  3. Select Enable Public Bug Board

Once enabled, a unique shareable URL is generated for your board. You can configure the board and copy the link from the Settings → Bugs page.

You can also access board settings through Quick Actions → Public Bug Board → Settings on the Bugs page.

Open the Settings → Bugs page — the shareable URL is displayed at the top of the Public Bug Board section. Click Copy to copy it to your clipboard.

Anyone with this link can view the board. No sign-in is required.

Tip: Share the link on your Discord server, Steam page, community forum, or anywhere your players gather.

Configuring the Board

The Settings → Bugs page lets you control exactly what visitors see on your public board.

Visible Columns

Choose which columns appear in the bug list table. Available columns include:

Column Description
Title Bug title (always shown)
Status Current status (e.g., Open, In Progress)
Priority Priority level
Heat Community interest indicator
Occurrence Number of times this bug has been reported
Created Date When the bug was first reported
Updated Date When the bug was last updated
Reported By Who reported the bug
Assigned To Who is working on it
Release Which release the bug is associated with
Duplicates Number of duplicate reports
Due Date When the bug is due
Ext. Links Links to external tracking systems

By default, the board shows: Title, Status, Priority, Heat, Created Date, and Occurrence.

Visible Statuses

Select which bug statuses appear on the board. By default, the board shows bugs with these statuses:

  • Open — New, unresolved bugs
  • In Progress — Bugs being actively worked on
  • Needs More Info — Bugs that need additional details

You can also enable:

  • Resolved — Bugs that have been fixed
  • Closed — Bugs that are no longer relevant
  • Won’t Fix — Bugs that won’t be addressed

When multiple statuses are visible, the board displays tabs so visitors can filter by status.

Sorting

Control the default sort order of the bug list:

  • Sort by: Heat (default), ID, Priority, Occurrence, Duplicates, Created Date, Updated Date, or Due Date
  • Direction: Descending (default) or Ascending

Display Limit

Set the maximum number of bugs shown on the board, from 1 to 100 (default: 25). This acts as a hard cap — only the top bugs (based on your sort order) will be visible, even if more bugs match the filters.

Commenting

When commenting is enabled, visitors can leave comments on individual bugs after signing in to BetaHub. When disabled, the board is completely read-only.

Commenting is off by default.

What Visitors See

Bug List

Visitors see a clean table of bugs with the columns you’ve configured. If multiple statuses are visible, tabs at the top let them filter by status. Clicking any bug row opens its detail page.

The project name is displayed at the top of the board. If your project is publicly accessible, the name links back to the project page.

Bug Detail Page

The detail page shows:

  • Bug title and status
  • Tags and labels (if any)
  • Description and steps to reproduce (if provided)
  • Screenshots (if attached) — developer-private media is automatically excluded
  • Metadata based on your visible column settings (priority, heat, reporter, etc.)
  • Comments section (if commenting is enabled)

Bug titles, descriptions, and steps to reproduce are filtered for profanity before being displayed, unless the project’s profanity filter has been disabled in Content Settings.

Disabling the Board

To disable the public bug board:

  1. Go to Quick Actions → Public Bug Board → Disable on the Bugs page, or click Disable Public Board on the Settings → Bugs page
  2. Confirm the action

Disabling the board immediately revokes the link. Anyone visiting the old URL will see a “Not Found” message. If you re-enable the board later, a new URL is generated — the old link will not work again.

See Also

BetaHub Help
AI