2018-06-06 11:20:05 -04:00
### Problem to solve
2016-08-23 06:28:11 -04:00
2019-01-17 16:17:54 -05:00
<!-- What problem do we solve? -->
2018-12-10 10:23:18 -05:00
### Target audience
2019-02-26 15:24:05 -05:00
<!--- For whom are we doing this? Include a [persona ](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ )
2019-01-23 16:10:36 -05:00
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 09:42:19 -05:00
2019-01-24 23:04:54 -05:00
Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply)
2019-01-21 09:42:19 -05:00
2019-02-26 15:24:05 -05:00
- Parker, Product Manager, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#parker-product-manager
2019-01-23 14:24:03 -05:00
/label ~"Persona: Product Manager"
2019-02-26 15:24:05 -05:00
- Delaney, Development Team Lead, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#delaney-development-team-lead
2019-01-23 14:24:03 -05:00
/label ~"Persona: Development Team Lead"
2019-02-26 15:24:05 -05:00
- Sasha, Software Developer, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#sasha-software-developer
2019-01-23 14:24:03 -05:00
/label ~"Persona: Software developer"
2019-01-21 09:42:19 -05:00
2019-02-26 15:24:05 -05:00
- Devon, DevOps Engineer, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#devon-devops-engineer
2019-01-23 14:24:03 -05:00
/label ~"Persona: DevOps Engineer"
2019-02-26 15:24:05 -05:00
- Sidney, Systems Administrator, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#sidney-systems-administrator
2019-01-23 14:24:03 -05:00
/label ~"Persona: Systems Administrator"
2019-02-26 15:24:05 -05:00
- Sam, Security Analyst, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#sam-security-analyst
2019-01-23 14:24:03 -05:00
/label ~"Persona: Security Analyst"
2019-01-21 09:42:19 -05:00
-->
2018-12-10 10:23:18 -05:00
2018-06-06 11:20:05 -04:00
### Further details
2019-01-17 16:17:54 -05:00
<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
2016-08-23 06:28:11 -04:00
2016-08-25 10:41:51 -04:00
### Proposal
2019-01-17 21:59:01 -05: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 10:23:18 -05:00
2019-02-27 02:34:16 -05:00
### Permissions and Security
What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
2019-01-10 21:41:02 -05:00
### Documentation
2019-02-08 13:18:47 -05:00
<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature - change - workflow.html
Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements -->
2019-01-10 21:41:02 -05:00
2018-06-06 11:20:05 -04:00
### What does success look like, and how can we measure that?
2019-01-17 21:59:01 -05: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 11:20:05 -04:00
2016-08-25 10:41:51 -04:00
### Links / references
2017-03-17 07:43:32 -04:00
2019-01-14 13:18:05 -05:00
/label ~feature
