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
• Let players vote on the bugs that matter most to them

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.

Sharing the Link

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.

Display Mode

The Display Mode setting controls which bugs appear on the board:

• Automatic (default) — Shows all bugs that match your status filters, sorted by your chosen sort order. The board updates automatically as new bugs come in and statuses change.
• Curated — Shows only the bugs you manually select. Use this when you want full control over exactly which bugs your community sees. In curated mode, the display limit and visible status filters do not apply — you manage the list directly.

To switch modes, change the Display Mode dropdown in the board settings and click Save Settings.

Adding Bugs in Curated Mode

When the board is set to curated mode, add bugs from your internal bugs view:

1. On the Bugs index page, click the row menu (⋯) on any bug and select Add To Public Board
2. On a Bug detail page, open Quick Actions and select Add To Public Board

To remove a bug from the curated list, use Remove From Public Board from the same menus.

Bugs appear on the curated board in the order you add them.

Visible Columns

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

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.

Note: In curated mode, the visible statuses filter does not restrict which bugs you can add — you can curate bugs with any status. The status tabs still appear for visitors to filter the curated list.

Sorting

Control the default sort order of the bug list:

• Sort by: Heat (default), ID, Priority, Votes, 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.

Note: The display limit does not apply in curated mode. All curated bugs are shown regardless of this setting.

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.

Voting

When voting is enabled, signed-in visitors can vote on bugs to signal which issues affect them. Each vote increases the bug’s heat score, helping the most impactful bugs rise to the top.

To enable voting:

1. Go to Settings → Bugs
2. Toggle Allow voting on
3. Click Save Settings

Voting is off by default.

How Voting Works

• A vote indicator (upvote arrow with count) appears as the first column on the bug list and next to the title on the detail page.
• Visitors must sign in to vote. Clicking the vote indicator when not signed in prompts the visitor to sign in; after signing in, they are returned to the board.
• Each visitor can vote once per bug. Clicking the indicator again removes the vote.
• Votes directly affect the bug’s heat score — more votes mean higher heat, which makes the bug more visible when sorted by heat.

Tip: Enable voting and set the sort order to “Votes” to let your community prioritize which bugs matter most.

Discord integration: If you use the Discord bot, community members can also vote on bugs by reacting with an emoji in Discord bug threads. Discord votes count toward the same heat score.

Redirecting Testers and Visitors

If you’d rather your testers and players never land on the internal bugs page at all, you can have BetaHub send them to the public bug board automatically. Turn on Redirect testers and visitors to this board in the board settings — anyone visiting the internal Bugs page who isn’t a developer, support member, organization admin, or BetaHub site administrator gets redirected to your public board instead.

This is useful when:

• You want a single front door for non-team users — players and testers shouldn’t see internal triage views
• You’re sharing the project URL more broadly (Discord, Steam page) and don’t want to teach everyone the public-board URL separately
• Curated/tester groups should still file bugs but only see what’s been made public

Who gets redirected

Enabling the redirect

1. Go to Settings → Bugs
2. Under Public Bug Board, toggle Redirect testers and visitors to this board on
3. Click Save Settings

The toggle is off by default. It only takes effect while the public bug board is enabled — if you disable the public board, the redirect goes inert until you re-enable it.

Deep links to specific bugs

If a non-team user follows a link to a specific bug (for example a stale link they bookmarked):

• If the bug is visible on the public board, they’re redirected to the same bug on the public board
• If the bug isn’t visible there (a closed status, hidden, etc.), they’re redirected to the public board’s main page

Public-link exemption

Bugs shared via a public link are exempt from the redirect. Anyone clicking the public link still lands on the linked bug, regardless of the toggle.

Previewing as a tester

Developers, organization admins, and site administrators can preview what testers and visitors experience by adding ?perspective=tester or ?perspective=non_member to the internal Bugs URL. You’ll stay on the internal page (so the team perspective preview keeps working) and an info banner will tell you where a real tester would have been redirected. Support members can’t use this preview — they always see the internal page as themselves.

Pinning Bugs

Pin important bugs to highlight them at the top of the board. Pinned bugs appear in a dedicated section above the main table, visually distinguished with an orange accent — making them impossible to miss.

This is useful for:

• Highlighting critical known issues your team is actively working on
• Drawing attention to bugs you want community input on
• Communicating important status updates to players

How to Pin a Bug

From the public board:

1. Navigate to a bug’s detail page on the public board
2. Click the Pin button in the top-right area of the header
3. The button changes to Pinned and the bug appears in the pinned section on the board list

From the internal bugs view:

1. On the Bugs index page, click the row menu (⋯) on any bug and select Pin On Public Board
2. On a Bug detail page, open Quick Actions and select Pin On Public Board

To unpin, use the same controls — the label switches to Unpin From Public Board or click the Pinned button on the public board detail page.

Note: Only project developers, organization admins, and site admins can pin and unpin bugs. Regular visitors will not see the pin controls.

Pinned Bugs and Status Filters

Pinned bugs are always shown in the pinned section regardless of the board’s visible status settings. For example, if you pin a “Resolved” bug but “Resolved” is not in your visible statuses, the pinned bug will still appear at the top of the board. This lets you highlight important bugs even after they’ve been fixed.

Bugs with internal-only statuses (hidden, duplicate, pending moderation) are automatically excluded from the pinned section.

What Visitors See

Bug List

Visitors see a clean table of bugs with the columns you’ve configured. If voting is enabled, a Votes column appears as the first column, showing an upvote arrow and vote count for each bug.

If you’ve pinned any bugs, they appear in a highlighted Pinned section above the table. Pinned bugs are not duplicated in the main table below.

If multiple statuses are visible, tabs at the top let visitors 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:

• A vote indicator next to the bug title (if voting is enabled) — visitors can vote or remove their vote directly
• A horizontal metadata bar with status, priority, and tags
• Description and steps to reproduce (if provided)
• A sidebar with heat score, report count, creation date, and other configured metrics
• Screenshots (if attached) — developer-private media is automatically excluded
• Comments section (if commenting is enabled)
• A Pin / Pinned button (visible to project developers only)

Bug titles, descriptions, and steps to reproduce are filtered for profanity before being displayed, unless the project’s profanity filter has been disabled in Project 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 Suggestions Board – Shareable public board for community suggestions
• Managing Feedback – Triage and workflow best practices
• Core Features – Feedback management essentials
• Project Settings – Configure project options