You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/epic_issue.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ assignees: ''
9
9
10
10
_[General guidance: When drafting a feature project, the goal is to create a reference for project scope and context. Write for our core product team. The issue should not be overly technical, and should be be comprehensible and a useful reference to devs, designers, and QA team, to build a shared source of understanding. Anyone at LE should be able to read this and more or less understand the project. If there is relevant information or context that is for the internal team only, please add that in a notion page and link it, rather than adding directly to these issues.]_
11
11
12
-
## Overview
12
+
## Overview
13
13
14
14
_[First, the project and purpose in one sentence, i.e.: Allow coaches and admins to customize quiz questions in Koilbri]_
15
15
@@ -18,23 +18,23 @@ _[Then, more detail]_
18
18
- Why are we doing this now?
19
19
- What feedback, requests, insights and/or concerns are shaping this feature? Include specific comments from partners, clearinghouse, or teammates as relevant.
20
20
21
-
### Contributors
22
-
_[Fill this out as people are assigned]_
21
+
### Contributors
22
+
_[Fill this out as people are assigned]_
23
23
- Technical lead: [github handle]
24
-
- Individual contributors: [list all github handles]
25
-
- Designer: [if a specific designer is leading]
24
+
- Individual contributors: [list all github handles]
25
+
- Designer: [if a specific designer is leading]
26
26
- Other relevant LE team members: [optional, i.e. imps point person]
27
27
28
28
### Goals
29
29
- Who is this feature for? Outline user stories below, but also mention if there is a specific partner and/or deployment
30
30
- How do we know this feature is successful?
31
31
32
32
#### User Stories or Requirements
33
-
_[Break down the main workflows thematically, but still at a high level. How are the goals of the project realized in the UI? If there isn't a UI portion of this project, what are the key outcomes or improvements? There should probably only be a few of these per project]_
33
+
_[Break down the main workflows thematically, but still at a high level. How are the goals of the project realized in the UI? If there isn't a UI portion of this project, what are the key outcomes or improvements? There should probably only be a few of these per project]_
34
34
35
35
### Target Quarter and Due date
36
36
- What is the timeline of this project?
37
37
- If there is a specific due date, especially for a contractual deliverable, include it. Otherwise, include an estimated delivery date, and what quarter(s) this will be worked on
38
38
39
-
### Product Issues
39
+
### Product Issues
40
40
_[Issues should be linked here as they are created. There will probably be 1-2 per User Story]_
0 commit comments