2018-06-06 15:20:05 +00:00
|
|
|
### Problem to solve
|
2016-08-23 10:28:11 +00:00
|
|
|
|
2018-12-10 15:23:18 +00:00
|
|
|
<!--- What problem do we solve? -->
|
|
|
|
|
|
|
|
### Target audience
|
|
|
|
|
2019-01-11 02:41:02 +00:00
|
|
|
<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/getting-started/personas
|
|
|
|
or define a specific company role. e.a. "Release Manager" or "Security Analyst" -->
|
2018-12-10 15:23:18 +00:00
|
|
|
|
2018-06-06 15:20:05 +00:00
|
|
|
### Further details
|
|
|
|
|
2018-12-10 15:23:18 +00:00
|
|
|
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) -->
|
2016-08-23 10:28:11 +00:00
|
|
|
|
2016-08-25 14:41:51 +00:00
|
|
|
### Proposal
|
|
|
|
|
2018-12-10 15:23:18 +00:00
|
|
|
<!--- How are we going to solve the problem? -->
|
|
|
|
|
2019-01-11 02:41:02 +00:00
|
|
|
### 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. -->
|
|
|
|
|
2018-06-06 15:20:05 +00:00
|
|
|
### What does success look like, and how can we measure that?
|
|
|
|
|
2018-12-10 15:23:18 +00:00
|
|
|
<!--- If no way to measure success, link to an issue that will implement a way to measure this -->
|
2018-06-06 15:20:05 +00:00
|
|
|
|
2016-08-25 14:41:51 +00:00
|
|
|
### Links / references
|
2017-03-17 11:43:32 +00:00
|
|
|
|
2017-11-09 17:43:39 +00:00
|
|
|
/label ~"feature proposal"
|