summaryrefslogtreecommitdiff
path: root/.gitlab/issue_templates/Release group - feature.md
diff options
context:
space:
mode:
Diffstat (limited to '.gitlab/issue_templates/Release group - feature.md')
-rw-r--r--.gitlab/issue_templates/Release group - feature.md26
1 files changed, 26 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Release group - feature.md b/.gitlab/issue_templates/Release group - feature.md
new file mode 100644
index 00000000000..0a695dac2ad
--- /dev/null
+++ b/.gitlab/issue_templates/Release group - feature.md
@@ -0,0 +1,26 @@
+## Problem to solve
+
+<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->
+
+## Proposal
+
+<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
+
+<!-- Default labels -->
+/label ~"group::release"
+/label ~"type::feature"
+/label ~"workflow::problem validation"
+/label ~UX
+
+<!-- Optional labels -->
+/label ~backend ~frontend
+
+<!-- If you already have an implementation plan, please fill in detail below https://about.gitlab.com/handbook/engineering/development/ops/release/planning/#weights -->
+/weight X
+/label ~"backend-weight::" ~"frontend-weight::" ~"workflow::ready for development"
+## Implementation guide
+
+<!-- If the issue clear enough, consider inviting community contributors -->
+/label ~"Seeking community contributions" ~"good for new contributors"
+
+