diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-09 15:11:06 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-09 15:11:06 +0300 |
commit | 6180f62ab34662c64103872b8352b25817b73a8d (patch) | |
tree | 2d7f30b845726fb0bff9ee191c11996c04c22c2c /.gitlab/issue_templates/Release group - feature.md | |
parent | 2e2db606cc7547b445a11c367d8db6f5feb42443 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/issue_templates/Release group - feature.md')
-rw-r--r-- | .gitlab/issue_templates/Release group - feature.md | 26 |
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" + + |