kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Updates to Feature proposal.md

This commit is contained in:
Mike Lewis 2019-01-17 21:17:54 +00:00
parent b2c6058a49
commit 343534f40f
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
.gitlab/issue_templates/Feature proposal.md
View File

@ -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