sift
Sign inStart free
engineering

Bug Report

Bug reports from users, QA, and internal teams arrive with wildly different quality and detail levels. This template extracts the component affected, steps to reproduce, expected vs actual behaviour, severity, environment details, and any error messages, turning messy reports into actionable tickets your engineering team can triage immediately.

See it in action

What users type

Found a bad one in production. When a user submits a form with more than 20 fields, the extraction API returns a 504 timeout after about 30 seconds. Tried it three times with our enterprise demo form (the 24-field insurance intake). Works fine with shorter forms. Chrome 124 on macOS. The spinner just hangs and then shows a generic error message instead of the extracted data. This is blocking our sales demo tomorrow. Reported by Wei Zhang.

What you get

Reporter

Wei Zhang

99%
Component / Feature

Extraction API

96%
Bug Summary

Extraction API returns 504 timeout on forms with more than 20 fields

97%
Steps to Reproduce

1. Submit a form with 20+ fields (e.g., 24-field insurance intake demo form). 2. Wait ~30 seconds. 3. Observe 504 timeout.

93%
Expected Behaviour

Extraction completes and returns structured data

92%
Actual Behaviour

Spinner hangs for 30 seconds, then 504 timeout with generic error message instead of extracted data

97%
Severity

Critical

94%
Environment

Production, Chrome 124, macOS

96%

Extracted fields

FieldTypeRequired
ReportertextRequired
Component / FeaturetextRequired
Bug SummarytextRequired
Steps to ReproducetextRequired
Expected BehaviourtextOptional
Actual BehaviourtextRequired
SeverityselectRequired
EnvironmenttextOptional

Use this template

Sign up and select “Bug Report” from the template gallery. Customise any field before going live.

Start with this template — free

Related