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.

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.

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
Key	Label	Type	Options
title	One-line summary	Text	-
severity	How bad is it?	Select	4
steps_to_reproduce	Steps to reproduce	Textarea	-
expected_vs_actual	What you expected vs what happened	Textarea	-
screenshot	Screenshot, screen recording, or HAR	File	-
email	Email for follow-up	Email	-

Product bug report

6 fields.

More in Forms.