generated from opentensor/bittensor-subnet-template
-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update and rename feature_request.md to feature_request.yml
- Loading branch information
1 parent
1101596
commit ec9c435
Showing
2 changed files
with
88 additions
and
21 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
name: Issue | ||
description: Create a new development task (feature, improvement, documentation, tests) | ||
title: "[Type]: " | ||
labels: ["task"] | ||
assignees: [] | ||
body: | ||
- type: dropdown | ||
id: priority | ||
attributes: | ||
label: Priority Impact | ||
description: Select the priority level for this issue | ||
options: | ||
- P0 - Critical (Immediate action required) | ||
- P1 - High (Urgent) | ||
- P2 - Medium (Important) | ||
- P3 - Low (Can be scheduled) | ||
validations: | ||
required: true | ||
- type: dropdown | ||
id: type | ||
attributes: | ||
label: Issue Type | ||
description: What kind of development task is this? | ||
options: | ||
- Feature Implementation | ||
- Technical Improvement | ||
- Documentation Update | ||
- Test Coverage | ||
- Technical Debt | ||
- Performance Optimization | ||
- Security Enhancement | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: description | ||
attributes: | ||
label: Technical Description | ||
description: Provide a clear technical description of what needs to be implemented | ||
placeholder: | | ||
Technical context: | ||
- What needs to be built/changed | ||
- Key technical considerations | ||
- Potential impact areas | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: acceptance-criteria | ||
attributes: | ||
label: Acceptance Criteria | ||
description: List specific, testable criteria that must be met for this task to be considered complete | ||
placeholder: | | ||
- [ ] Criterion 1 | ||
- [ ] Criterion 2 | ||
- [ ] Unit tests added/updated | ||
- [ ] Documentation updated | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: technical-details | ||
attributes: | ||
label: Implementation Details | ||
description: Provide technical details, architecture decisions, or implementation guidance | ||
placeholder: | | ||
- Technical approach | ||
- API changes | ||
- Database changes | ||
- Configuration changes | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: dependencies | ||
attributes: | ||
label: Dependencies | ||
description: List any technical dependencies or prerequisites | ||
placeholder: | | ||
- Related PRs | ||
- System dependencies | ||
- External services | ||
validations: | ||
required: true | ||
- type: input | ||
id: estimated-effort | ||
attributes: | ||
label: Estimated Effort | ||
description: Provide a rough estimate of the development time required | ||
placeholder: e.g., 3 story points, 2 days | ||
validations: | ||
required: true |