Skip to content

Product bug report

Severity, reproduction steps, and evidence for engineering.

Product
Forms
Fields
6, 5 required
Best for
Product quality
Goes to
Triage to engineering with evidence attached.

No card needed. Ready in about three minutes.

Live preview. Try it.Open in new tab
What arrives
{
  "title": "Checkout fails when coupon is applied",
  "severity": "How bad is it?",
  "steps_to_reproduce": "Steps to reproduce",
  "expected_vs_actual": "What you expected vs what happened",
  "screenshot": "Screenshot, screen recording, or HAR",
  "email": "name@example.com"
}

Sample values.

Every answer lands as a structured record in your inbox, with the same keys in exports, the API, and signed webhooks.

What you get, and what it needs.

  • 6 fields, 5 required
  • A file upload field, which needs storage on Pro and up

Installing creates a new item in your own workspace from the template definition. Nothing is copied from anyone else's account: no contacts, no credentials and no submissions.

  1. Choose Use this template

    If you are signed out you sign up or sign in first, and the template you picked carries through.

  2. The builder opens with it applied

    Your new form starts as a draft. Change the fields, the logic and the look.

  3. Publish and share

    Publish it, then share the link, embed it on your site, or print its QR code.

6 fields.

Rename a label, swap an option, or add logic. The keys stay stable for your integrations.

Fields in the Product bug report template
KeyLabelTypeOptions
titleOne-line summaryText-
severityHow bad is it?Select4
steps_to_reproduceSteps to reproduceTextarea-
expected_vs_actualWhat you expected vs what happenedTextarea-
screenshotScreenshot, screen recording, or HARFile-
emailEmail for follow-upEmail-