diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-16 15:09:12 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-16 15:09:12 +0300 |
| commit | cbfe03ae04a52d9825ff7cbeccdfe5d313adf6a2 (patch) | |
| tree | e4879b35d019d3bbba1689f3ac4c48b81bf7b451 /.gitlab/issue_templates | |
| parent | 3fd97b4bba24ca412112aad025a38a32c7a6cf8c (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/issue_templates')
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index 4e52a69f415..2bbef723b21 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -59,6 +59,10 @@ See the test engineering planning process and reach out to your counterpart Soft <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> +### Is this a cross-stage feature? + +<!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> + ### Links / references /label ~feature |