diff options
| author | Mike Lewis <mlewis@gitlab.com> | 2019-01-18 00:20:27 +0300 |
|---|---|---|
| committer | Mike Lewis <mlewis@gitlab.com> | 2019-01-18 00:20:27 +0300 |
| commit | 81e5f80e88622e93bf6e05a266fd7428a35d1d5a (patch) | |
| tree | 7410e6a5288cd90fc550144e4d4ba450e2fc4c85 /.gitlab | |
| parent | 343534f40fa1b3babd2694a6437c7cb7ef43e0b6 (diff) | |
Minor edits to Feature proposal template
Diffstat (limited to '.gitlab')
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index adf302996f0..5987d35a3d2 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -19,7 +19,7 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst" <!-- * What doc pages need to be created or updated across user, admin, and API docs? -* What concepts, procedures, or information is needed in each area? Is there an 'old way' or workaround to deprecate? +* What concepts, procedures, or information is needed in each area? Is there an 'old way' to deprecate in docs? Product managers: * By the kickoff, finalize the answers to the bullets above, and: |