Asset-Frameworker/Tickets/_template.md
2025-04-29 18:26:13 +02:00

1.5 KiB

ID, Type, Status, Priority, Labels, Created, Updated, Related
ID Type Status Priority Labels Created Updated Related
TYPE-XXX Issue | Feature Backlog | Planned | In Progress | Blocked | Needs Review | Done | Won't Fix Low | Medium | High
gui
cli
core
blender
bug
feature
enhancement
docs
config
YYYY-MM-DD YYYY-MM-DD

[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.