Oliver Jägle
commited on
Add epic template
Browse files
.github/ISSUE_TEMPLATE/epic.md
ADDED
|
@@ -0,0 +1,23 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
name: Epic
|
| 3 |
+
about: Epics define long-term vision and capabilities of the software. They will never be finished but serve as umbrellas for features.
|
| 4 |
+
title: ''
|
| 5 |
+
labels:
|
| 6 |
+
- epic
|
| 7 |
+
assignees: ''
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
# Strategic Impact
|
| 11 |
+
|
| 12 |
+
<-- Why does this area matter? How is it integrated into the product or the development process? What would happen if we ignore it? -->
|
| 13 |
+
|
| 14 |
+
# Target Audience
|
| 15 |
+
|
| 16 |
+
<!-- Who benefits most from improvements in this area?
|
| 17 |
+
|
| 18 |
+
Usual values: Software Developers using the IDE | Contributors -->
|
| 19 |
+
|
| 20 |
+
# Capabilities
|
| 21 |
+
|
| 22 |
+
<!-- which existing capabilities or future features can be imagined that belong to this epic? This list serves as illustration to sketch the boundaries of this epic.
|
| 23 |
+
Once features are actually being planned / described in detail, they can be linked here. -->
|