30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
---
|
|
ID: TYPE-XXX # e.g., FEAT-001, ISSUE-002
|
|
Type: Issue | Feature # Choose one: Issue or Feature
|
|
Status: Backlog | Planned | In Progress | Blocked | Needs Review | Done | Won't Fix # Choose one
|
|
Priority: Low | Medium | High # Choose one
|
|
Labels: [gui, cli, core, blender, bug, feature, enhancement, docs, config] # Add relevant labels from the list or define new ones
|
|
Created: YYYY-MM-DD
|
|
Updated: YYYY-MM-DD
|
|
Related: # Links to other tickets (e.g., #ISSUE-YYY), relevant files, or external URLs
|
|
---
|
|
|
|
# [TYPE-XXX]: Brief Title of Issue/Feature
|
|
|
|
## Description
|
|
(Provide a detailed explanation of the issue or feature request. What is the problem you are trying to solve, or what is the new functionality you are proposing?)
|
|
|
|
## Current Behavior
|
|
(Describe what happens currently. If reporting a bug, explain the steps to reproduce it. If proposing a feature, describe the current state without the feature.)
|
|
|
|
## Desired Behavior / Goals
|
|
(Describe what *should* happen if the issue is resolved, or what the feature aims to achieve. Be specific about the desired outcome.)
|
|
|
|
## Implementation Notes (Optional)
|
|
(Add any thoughts on how this could be implemented, potential technical challenges, relevant code sections, or ideas for a solution.)
|
|
|
|
## Acceptance Criteria (Optional)
|
|
(Define clear, testable criteria that must be met for the ticket to be considered complete.)
|
|
* [ ] Criterion 1: The first condition that must be satisfied.
|
|
* [ ] Criterion 2: The second condition that must be satisfied.
|
|
* [ ] Add more criteria as needed. |