Submit Report | StreamSuites Developer Console

Required issue definition

Core report

Keep the title short, mark severity honestly, and describe how to reproduce the issue with exact steps.

TitleRequired Short technical summary used in triage lists. CategoryRequired Choose the dominant issue type. SeverityRequired Pick the current user-facing impact.

Affected areaRequired Select every surface or subsystem touched by this issue.

Dashboard shellAuthenticated console sidebar, topbar, and shell layout. Reports hubProtected `/reports` hub routing and launch points. Report submissionStandalone `/reports/submit` form flow and validation. Keys workspaceProtected `/keys` placeholder route and account gating. Auth / sessionLogin, redirects, cookies, gating, or session bootstrap. API / backendRequest payloads, API failures, runtime authority, or response shape. Runtime / exportsData export, artifact handling, or operational background state. OtherUse when none of the listed areas fit.

Reproduction stepsRequired List the exact steps, state transitions, and timing needed to reproduce. Expected resultRequired What should have happened instead. Actual resultRequired What happened in reality, including user-visible impact.

Structured diagnostics

Environment / browser

Capture the execution context as discrete fields so triage does not depend on parsing one loose paragraph.

Operating systemRequired Name the OS family where the issue occurred. OS versionOptional Add build or release detail when it matters. BrowserRequired Name the browser or client shell involved. Browser versionOptional Include the exact version if available. Viewport / screen sizeOptional Useful for responsive or shell-spacing issues. Device typeRequired Call out the device class involved. Active flags / experimental toggles / extensions / special conditionsOptional Only include conditions that materially affect reproduction.

Structured context

Platform / account context

Split route, surface, platform, and account scope into discrete fields so the backend still receives a predictable summary.

SurfaceRequired Primary StreamSuites surface or shared subsystem where the issue occurred. PlatformOptional Use when an external platform or integration matters. Route / URL pathRequired Use a route or scrubbed path, not a full secret-bearing URL. Creator contextOptional Creator state or role relevant to the bug. Viewer contextOptional Viewer-side scenario relevant to the bug. Account / tier contextOptional Safe role or tier information only. No secrets. Relevant creator / viewer identifiersOptional Safe identifiers only when they materially help triage.

Technical detail

Notes and attachments

Preserve the richer developer-report detail while making required versus optional fields explicit.

Detailed notesRequired Capture mitigation attempts, extra observations, or edge-case findings that do not fit elsewhere. Advanced structured metadata (JSON)Optional Optional extra JSON merged into the structured metadata payload after validation. AttachmentsOptional Safe file types only in this phase: images, JSON, TXT, and LOG files.

Submit a technical report

Core report

Environment / browser

Platform / account context

Notes and attachments