Sign inSign up

Report forms

One form for visitors. Another for the team.

An admin decides what a visitor is asked, and what a signed-in teammate is asked. Each field can be visible or hidden, required or optional. The widget reads that config when the report opens.

Create a workspaceSee a demo

The fields

Title, description, priority, type, and who filed it.

Type can be a bug, feedback, a question, or other. Priority can be low, medium, high, or critical. The defaults below are what a new workspace starts with. An admin can change them under Settings → Forms.

  • Guests, by default

    Title, description, and name are required. Priority, type, and email are visible and optional. This is the form a visitor gets when the script tag leaves data-audience off, or sets it to guest.

  • Members, by default

    Title, description, priority, and type are required. Name and email are hidden, because the account is already known. Set data-audience="member" on a build your teammates use.

  • Visible, and required, are separate

    A field can be on the form without being mandatory. Hide a field and the reporter is not asked for it. The widget follows the config for that audience.

  • The page URL comes along either way

    The form is the part a person fills in. The screenshot, the element, the replay, the console, the network, and the environment are attached whether or not those fields are on the form.

On the $5 plan

A visitor can file a bug without an account.

Guest reporting is on the $5 plan. The widget audience on the script tag is separate from a person’s role in the dashboard. data-audience picks the form. The team page covers admin, member, and guest roles.

Roles in the workspace

Also included

The rest of the product.

BugTrap

$5 a month for the workspace. The team is included.

Screenshot, markup, element HTML and CSS, replay, diagnostics, guest reports, Asana, and MCP come with that price.

Create a workspaceSee a demo