Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update epic_template.md #1072

Merged
merged 2 commits into from
Oct 30, 2024
Merged

Update epic_template.md #1072

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0aabccb
Update epic_template.md
SebastianOpriel Oct 28, 2024
f20bf5a
Merge branch 'main' into adjust-templates1
efiege Oct 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/ISSUE_TEMPLATE/epic_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ assignees: ""

### Requirements
<!-- Which requirements do you have to be fulfilled? -->
<!-- Which security-related requirements must be satisfied? -->

## Work Breakdown
<!-- If you already know what needs to be done, plase add a tasklist. -->
Expand All @@ -22,14 +23,18 @@ assignees: ""
- [ ] Create Stories which can be converted into issues
```

### Security Constraints
<!-- Which constraints can be checked that must be covered by the work breakdown? -->
- [ ] Final solution design has been challenged for security related topics

## Initiative / goal
<!-- Describe how this Epic impacts an initiative the business is working on. -->

### Hypothesis
<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->

## Acceptance criteria and must have scope
<!-- Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->

## Stakeholders
<!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->
Expand Down
Loading