Files
cozystack/.github/ISSUE_TEMPLATE/feature_request.md
T
Aleksei Sviridkin 4cbfb31348 chore(github): auto-label new issues triage/needs-triage
Every issue created through a template now gets triage/needs-triage so
the untriaged backlog is visible at a glance and the stale bot's 60-day
clock has a clear signal for maintainers to act on.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-07-16 20:10:20 +03:00

43 lines
1.4 KiB
Markdown

---
name: Feature request
about: Propose a concrete, scoped improvement to Cozystack
labels: 'kind/feature, triage/needs-triage'
assignees: ''
---
<!--
Before you file, make sure this is the right place:
• A usage question or a half-formed idea?
→ Start a GitHub Discussion instead: https://github.com/cozystack/cozystack/discussions
• A cross-cutting or architectural change — one that affects multiple components
or APIs, or that needs a decision agreed before any code is written?
→ Open a design proposal in the community repo:
https://github.com/cozystack/community/tree/main/design-proposals
This template is for a CONCRETE, SCOPED feature that a maintainer could pick up
and implement without first settling an open design question.
-->
**Problem / motivation**
What are you trying to do, and what is missing or painful today?
**Proposed solution**
What should Cozystack do? Be as concrete as you can — the API field, flag, value, or behavior you expect.
**Scope check**
- [ ] This affects a single component / package (if it spans many, consider a [design proposal](https://github.com/cozystack/community/tree/main/design-proposals))
- [ ] I can describe the expected behavior concretely (if not, consider a [Discussion](https://github.com/cozystack/cozystack/discussions) first)
**Alternatives considered**
Other approaches you weighed, and why this one.
**Additional context**
Links, related issues, screenshots, prior art.