2018-06-06 15:20:05 +00:00
### Problem to solve
2016-08-23 10:28:11 +00:00
2019-01-17 21:17:54 +00:00
<!-- What problem do we solve? -->
2018-12-10 15:23:18 +00:00
### Target audience
2019-01-23 21:10:36 +00:00
<!--- For whom are we doing this? Include a [persona ](https://design.gitlab.com/research/personas )
listed below, if applicable, along with its [label ](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A ),
or define a specific company role, e.g. "Release Manager".
2019-01-21 14:42:19 +00:00
2019-01-25 04:04:54 +00:00
Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply)
2019-01-21 14:42:19 +00:00
- Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker
2019-01-23 19:24:03 +00:00
/label ~"Persona: Product Manager"
2019-01-21 14:42:19 +00:00
- Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
2019-01-23 19:24:03 +00:00
/label ~"Persona: Development Team Lead"
2019-01-21 14:42:19 +00:00
- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
2019-01-23 19:24:03 +00:00
/label ~"Persona: Software developer"
2019-01-21 14:42:19 +00:00
- Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
2019-01-23 19:24:03 +00:00
/label ~"Persona: DevOps Engineer"
2019-01-21 14:42:19 +00:00
- Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney
2019-01-23 19:24:03 +00:00
/label ~"Persona: Systems Administrator"
2019-01-21 14:42:19 +00:00
- Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam
2019-01-23 19:24:03 +00:00
/label ~"Persona: Security Analyst"
2019-01-21 14:42:19 +00:00
-->
2018-12-10 15:23:18 +00:00
2018-06-06 15:20:05 +00:00
### Further details
2019-01-17 21:17:54 +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
2019-01-18 02:59:01 +00:00
<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user - journey -->
2018-12-10 15:23:18 +00:00
2019-01-11 02:41:02 +00:00
### Documentation
2019-01-30 17:47:54 +00:00
<!-- See the Documentation Workflows https://docs.gitlab.com/ee/development/documentation/workflow.html and specify the following:
What doc pages need to be created or updated across user, admin, and API docs?
2019-01-23 05:43:03 +00:00
What concepts, procedures, or information is needed in each area? Is there an 'old way' that should be deprecated in the docs?
2019-01-30 17:47:54 +00:00
If applicable, specify a new or updated feature name, description, benefits, and use cases, which may all be used in the documentation or features.yml.
Which use cases or scenarios would benefit from a set of instructions or a guide, whether unique to each use case or flexible enough to cover multiple use cases. -->
2019-01-11 02:41:02 +00:00
2018-06-06 15:20:05 +00:00
### What does success look like, and how can we measure that?
2019-01-18 02:59:01 +00:00
<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is 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
2019-01-14 18:18:05 +00:00
/label ~feature
