feat(config): add issue templates for Epics, User Stories, and Subtasks
This commit is contained in:
46
.gitea/ISSUE_TEMPLATE/epic.md
Normal file
46
.gitea/ISSUE_TEMPLATE/epic.md
Normal file
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: "Epic"
|
||||
about: "A large initiative or feature that consists of multiple User Stories or Subtasks"
|
||||
title: "[Epic] <Epic title>"
|
||||
labels: ["Type/Epic"]
|
||||
---
|
||||
|
||||
## 🧩 Epic Summary
|
||||
Provide a clear summary of what this Epic aims to achieve.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Goals
|
||||
- [ ] Goal 1
|
||||
- [ ] Goal 2
|
||||
- [ ] Goal 3
|
||||
|
||||
---
|
||||
|
||||
## 📋 Description
|
||||
Describe the high-level context, purpose, and expected outcome of this Epic.
|
||||
|
||||
---
|
||||
|
||||
## 🧵 Related User Stories / Subtasks
|
||||
Link to related issues here:
|
||||
- [ ] #<user-story-1>
|
||||
- [ ] #<user-story-2>
|
||||
- [ ] #<subtask-1>
|
||||
|
||||
---
|
||||
|
||||
## 📅 Milestone / Timeline
|
||||
If applicable, note any key dates or milestones:
|
||||
- Target Start:
|
||||
- Target Completion:
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ Risks / Dependencies
|
||||
List any major risks or dependencies that could affect delivery.
|
||||
|
||||
---
|
||||
|
||||
## ✅ Acceptance Criteria
|
||||
Define the success metrics or completion definition for the Epic.
|
||||
35
.gitea/ISSUE_TEMPLATE/subtask.md
Normal file
35
.gitea/ISSUE_TEMPLATE/subtask.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
name: "Subtask"
|
||||
about: "A smaller task that contributes to a User Story or Epic"
|
||||
title: "[Subtask] <Task title>"
|
||||
labels: ["Type/Subtask"]
|
||||
---
|
||||
|
||||
## 🧾 Description
|
||||
Briefly describe what needs to be done for this subtask.
|
||||
|
||||
---
|
||||
|
||||
## 🔗 Linked Issues
|
||||
- Parent Story: #<user-story-number>
|
||||
- Related Epic: #<epic-number>
|
||||
|
||||
---
|
||||
|
||||
## ⚙️ Steps / Tasks
|
||||
- [ ] Task 1
|
||||
- [ ] Task 2
|
||||
- [ ] Task 3
|
||||
|
||||
---
|
||||
|
||||
## ✅ Definition of Done
|
||||
What must be true for this subtask to be considered complete:
|
||||
- [ ] Code implemented
|
||||
- [ ] Tests passed
|
||||
- [ ] Reviewed and merged
|
||||
|
||||
---
|
||||
|
||||
## 🧩 Estimated Size
|
||||
Use label: `Size/XS` | `Size/S` | `Size/M` | `Size/L` | `Size/XL`
|
||||
42
.gitea/ISSUE_TEMPLATE/user_story.md
Normal file
42
.gitea/ISSUE_TEMPLATE/user_story.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
name: "User Story"
|
||||
about: "A feature or requirement from the user's perspective"
|
||||
title: "[Story] <User story title>"
|
||||
labels: ["Type/User Story"]
|
||||
---
|
||||
|
||||
## 🧍♂️ User Story
|
||||
**As a** [type of user]
|
||||
**I want to** [perform an action]
|
||||
**So that** [achieve a goal or value]
|
||||
|
||||
---
|
||||
|
||||
## 📋 Description
|
||||
Provide additional context or business logic for this story.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Acceptance Criteria
|
||||
List the specific, measurable criteria that define when this story is done:
|
||||
- [ ] Criterion 1
|
||||
- [ ] Criterion 2
|
||||
- [ ] Criterion 3
|
||||
|
||||
---
|
||||
|
||||
## 🧱 Implementation Notes
|
||||
Include technical notes, design references, or constraints.
|
||||
|
||||
---
|
||||
|
||||
## 🧵 Linked Issues
|
||||
- Parent Epic: #<epic-number>
|
||||
- Related Subtasks:
|
||||
- [ ] #<subtask-1>
|
||||
- [ ] #<subtask-2>
|
||||
|
||||
---
|
||||
|
||||
## 🧩 Estimated Size
|
||||
Use label: `Size/XS` | `Size/S` | `Size/M` | `Size/L` | `Size/XL`
|
||||
Reference in New Issue
Block a user