Template — Bug
Use this content in a Forgejo Issue.
Summary
One sentence describing the incorrect behavior and affected system.
Classification
- Severity: S0 / S1 / S2 / S3 / S4
- Labels:
type/...,area/...,risk/... - Baseline ID:
- Server artifact / full commit:
- Client snapshot/build:
- First known affected version:
- Last known working version:
Environment
Operating system, architecture, database/toolchain versions, manager revision, and relevant isolation/network setup.
Reproduction
- Start from
<clean state>. <step>- Observe
<result>.
Expected result
An observable outcome.
Actual result
An observable outcome, frequency, and whether retry/restart changes it.
Evidence
Sanitized logs, finding IDs, artifact IDs/hashes, minimal fixtures, screenshots, or captures. Never attach credentials, personal data, or restricted binaries to a public issue.
Data-loss and security impact
What can be corrupted, exposed, or made unrecoverable? If sensitive, move details to the private reporting path.
Workaround
Document a safe workaround or none known.
Fix acceptance
- Root cause recorded.
- Test fails before and passes after the fix.
- Clean install and upgrade paths checked where relevant.
- Backup and rollback tested for destructive changes.
- Affected wiki profile/baseline/finding updated.
Private Server Preservation
- Home
- Preservation Status
- Compatibility Matrix
- Ecosystem Map
- Vision and Scope
- Server Catalog
- Client Preservation
- Archive Layout
- Repository Mirroring
- Mirror Inventory
- Preservation Metadata
- Reverse Engineering
- Findings Log
- Bug Tracker
- Toolbox
- Reproducible Baselines
- Operational Runbooks
- Backup and Recovery
- Governance and Safety
- Contributing
- Templates
PrivateServer-RS preservation wiki · Originals remain immutable · Every artifact must be attributable and verifiable