← Docs

Recipe: Bug ticket + feature request templates

Standardised templates so every report lands with enough signal to ship a fix or spec a feature without a three-round interrogation.

Bug ticket

**Title** – [Component] Short description

**Build** – Nimbus v2.4.1 (2026-05-26)
**OS** – Windows 11 23H2 (22631.3593)

**Steps**
1. Launch Nimbus with config X
2. Click Y
3. Observe Z

**Expected** – What should happen
**Actual** – What happens instead (screenshot / log)

**Repro rate** – 3/3 or intermittent
**First seen** – 2026-05-26 14:30 UTC

Feature request

**Summary** – One-line pitch

**User story**
As a <role>, I want <capability> so that <outcome>.

**Current workaround** – What users do today
**Proposed UX** – Flow, mockup link, or wireframe

**Success metric** – How we know it shipped right
**Dependencies** – Backend, licensing, CDN, etc.

Tip — paste the template into a new GitHub Issue, Linear task, or Discord thread. The structured format cuts triage time by more than half.

Meridian © 2026 FoogleGiber LLC