diff options
| author | Mike Lewis <mlewis@gitlab.com> | 2019-01-17 21:17:54 +0000 |
|---|---|---|
| committer | Mike Lewis <mlewis@gitlab.com> | 2019-01-17 21:17:54 +0000 |
| commit | 343534f40fa1b3babd2694a6437c7cb7ef43e0b6 (patch) | |
| tree | 0ffa1fc5cc39f215a96aa8d34283623cdf23ea57 | |
| parent | b2c6058a499d707cec84e6da552dfa6ee1b3bbd4 (diff) | |
| download | gitlab-ce-343534f40fa1b3babd2694a6437c7cb7ef43e0b6.tar.gz | |
Updates to Feature proposal.md
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 21 |
1 files changed, 14 insertions, 7 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index 01eabde604e..adf302996f0 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -1,6 +1,6 @@ ### Problem to solve -<!--- What problem do we solve? --> +<!-- What problem do we solve? --> ### Target audience @@ -9,21 +9,28 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst" ### Further details -<!--- Include use cases, benefits, and/or goals (contributes to our vision?) --> +<!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal -<!--- How are we going to solve the problem? --> +<!-- How are we going to solve the problem? --> ### Documentation -<!-- What doc pages need to be created or updated across user, admin, and API docs? -What concepts, procedures, or info is needed on each? -PMs: Specify feature name, description, benefits, and use cases, if applicable. --> +<!-- +* 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? + +Product managers: +* By the kickoff, finalize the answers to the bullets above, and: + * If applicable, specify new or updated feature name(s), description(s), benefits, + and use cases, which may all be used in the documentation or features.yml. + * Specify which use cases or scenarios would benefit from a set of instructions + or a guide unique to that use case. --> ### What does success look like, and how can we measure that? -<!--- If no way to measure success, link to an issue that will implement a way to measure this --> +<!-- If no way to measure success, link to an issue that will implement a way to measure this --> ### Links / references |