Add latest changes from gitlab-org/gitlab@master

3 files changed, 87 insertions, 0 deletions

diff --git a/.gitlab/issue_templates/Release group - bug.md b/.gitlab/issue_templates/Release group - bug.md
new file mode 100644
index 00000000000..f542041593f
--- /dev/null
+++ b/.gitlab/issue_templates/Release group - bug.md
@@ -0,0 +1,43 @@
+## Summary
+
+<!-- Summarize the bug encountered concisely. -->
+
+## Steps to reproduce
+
+<!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->
+
+## What is the current *bug* behavior?
+
+<!-- Describe what actually happens. -->
+
+## What is the expected *correct* behavior?
+
+<!-- Describe what you should see instead. -->
+
+## Relevant logs and/or screenshots
+
+<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
+ as it's tough to read otherwise. -->
+
+## Possible fixes
+
+<!-- If you can, link to the line of code that might be responsible for the problem. -->
+
+<!-- Default labels -->
+/label ~"group::release"
+/label ~"type::bug"
+/label ~"workflow::planning breakdown"
+
+<!-- Optional labels -->
+/label ~backend ~frontend ~UX
+
+<!-- https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity -->
+/label ~"severity::3" ~"priority::3"
+
+<!-- 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"
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"
+
+
diff --git a/.gitlab/issue_templates/Release group - maintenance.md b/.gitlab/issue_templates/Release group - maintenance.md
new file mode 100644
index 00000000000..aa87015a44a
--- /dev/null
+++ b/.gitlab/issue_templates/Release group - maintenance.md
@@ -0,0 +1,18 @@
+## Background
+
+## 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. -->
+
+<!-- Set labels and other metadata -->
+/label ~"group::release"
+/label ~"type::maintenance"
+/label ~"workflow::planning breakdown"
+
+<!-- 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"