Skip to content

Public feature board

The public board is the customer-facing site where people browse feature requests, submit ideas, vote, and comment. URLs are shareable links your team distributes (for example from your product or docs).

How URLs are structured

Paths follow this pattern:

/{teamSlug}/{projectSlug}/boards/{boardSlug}

  • Team — Identifies the organization (human-readable slug in the URL).
  • Project — A product or area within that team.
  • Board — A specific feedback board with its own requests and workflow.

You may also see:

  • /…/boards/{boardSlug}/requests/{requestId} — A single request’s detail page.
  • /…/boards/{boardSlug}/new — The Submit a request form.
  • /…/boards/{boardSlug}/roadmap — The Roadmap view for the same board.

Query parameters on the board (for example filters and sort) are preserved when you switch between Requests and Roadmap so your context is not lost.

Requests view vs Roadmap

On a board, two tabs appear:

  • Requests — The main list of ideas with filters and sorting.
  • Roadmap — A timeline-style view of work, when your team configures statuses to appear on the roadmap.

Browsing and finding requests

  • Search — Narrow the list with the search field (updates the URL so links can be shared).
  • Status — On the Requests tab, filter by workflow status when statuses are enabled for filtering.
  • Tags — Filter by one or more tags when the project defines tags.
  • Sort — Choose Top Voted, Newest, or Recently Updated.

Open a request from the list to read the full description, discussion, and voting controls.

Submitting a request

  1. From the board, go to the flow labeled Submit a request (or open the /new URL for that board).
  2. Enter a title (required) and optional description.
  3. If you are not signed in, the form may show a Contact section with Email so the team can notify you about updates. If you are signed in, that section is omitted and your account is associated with the request.
  4. Optionally pick tags when the board offers them.
  5. Choose Submit. You are taken to the new request’s page after a successful submit.

Private projects

If a project is private, anonymous visitors may not be able to view or submit requests. Sign in when prompted, or use a link from your team if access is restricted.

Editing your request

If you submitted a request while signed in, the request detail page shows an Edit button next to the title. Use it to update the title and description in place — no need to switch to internal tooling.

  • The Edit button only appears when you are signed in and own the request (super admins also see it for any request).
  • It is hidden when the request is locked by the team.
  • Save your changes to update the request immediately; the page refreshes with the new content.
  • Validation, permission, and connection problems are shown in the form with actionable copy (for example, an expired session prompts you to sign in again).

If you do not see the Edit button on a request you submitted, confirm you are signed in with the same account you used when submitting, and check that the request is not locked.

Voting

On a request detail page, use Upvote to add your vote, or Voted to remove it if the product allows toggling.

  • If you are not signed in, the Upvote control may prompt you to sign in first—voting requires an authenticated session on most boards.

When you submit a request while signed in, the app may automatically add your upvote to that request.

Comments

The request detail page always shows a Comments section so you can read the discussion and contribute when you have access.

  • Signed in — A composer appears at the top of the section. Type your comment and choose Post comment. After a successful post, the new comment appears in the thread without a full page reload and the composer clears.
  • Not signed in — Instead of a composer, you see a Sign in prompt that returns you to the same request after authentication so you can post without losing your place.
  • Locked requests — When the team locks a request, the composer is replaced with a notice that new comments are not being accepted, and the Edit button is hidden on existing comments.
  • Editing your own comments — On comments you authored, an inline Edit button appears next to the comment. Choosing it swaps the comment for a textarea prefilled with the current text; Save updates the comment and shows a brief confirmation, and Cancel discards your edits without saving. The same 5,000-character limit applies. Other people's comments do not show an Edit button — only the author can edit. Comments that have been edited show a small · edited indicator next to the date (hover for the exact update time).
  • Limits — Comments are plain text and limited to 5,000 characters. Empty submissions are blocked.
  • Errors — Connection, permission, validation, and session problems are surfaced in the composer with actionable copy (for example, an expired session prompts you to sign in again).

Anonymous commenting is not supported — posting a comment always requires a signed-in account, even on boards that allow anonymous request submission.

Getting help

If a page does not load or you see “not found,” the slug may be wrong or the project may not be public. Contact the team that shared the board link.