Generator Szablonu Raportu o Błędach

Dane wejściowe

Project Info

Open-source React + TypeScript web app, Vite build, deployed on Vercel. Supports Chrome, Firefox, Safari. Components: auth, dashboard, billing. Community contributors file issues; we need a clear reproducible template.

Severity Levels

4-level

Project Type

web-app

Tracking Tool

github

Wynik (fragment)

## Bug Report
**Severity:** Critical / High / Medium / Low
**Environment:** Browser + version, OS, app version/commit
**Component:** auth / dashboard / billing
### Steps to Reproduce
1. ...
2. ...
### Expected Behavior
### Actual Behavior
### Screenshots / Console Output
### Reproducible?
- [ ] Always - [ ] Intermittent - [ ] Once
### Additional Context
<!-- Add labels and link related issues -->

Dane wejściowe

Project Info

Native mobile app (iOS Swift + Android Kotlin) for a fitness brand. QA team logs bugs in Jira. Need device, OS version, app build, and crash-log fields. Common issues: sync, push notifications, in-app purchases.

Severity Levels

5-level

Project Type

mobile-app

Tracking Tool

jira

Wynik (fragment)

Summary: [Component] short description
Severity: Blocker / Critical / Major / Minor / Trivial
Platform: iOS / Android | OS version: | App build:
Device/model:
Affected area: Sync / Push / In-App Purchase / Other
Steps to Reproduce:
1. 2. 3.
Expected Result:
Actual Result:
Frequency: Always / Sometimes / Once
Attachments: screen recording, crash log (Crashlytics ID)
Regression? Yes/No — last known good build:

Dane wejściowe

Project Info

Internal REST + GraphQL API service in Go, deployed on Kubernetes. Engineers track work in Linear. We need bug reports that include endpoint, request payload, response, status code, and trace ID for observability.

Severity Levels

3-level

Project Type

api

Tracking Tool

linear

Wynik (fragment)

Title: [API] <endpoint> returns <status>
Priority: Urgent / High / Normal
Endpoint & method: e.g. POST /v1/orders
Environment: prod / staging | Service version:
Request (headers + body, redact secrets):
Expected response:
Actual response (status code + body):
Trace ID / log link:
Reproducible? Always / Sometimes
Impact: affected users or downstream services
Suggested owner / related issue: