gitlab-org--gitlab-foss/.gitlab/issue_templates/Feature proposal.md

### Problem to solve

<!-- What problem do we solve? -->

### Target audience

<!--- 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".

Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply)

- Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker
/label ~"Persona: Product Manager"

- Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
/label ~"Persona: Development Team Lead"

- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
/label ~"Persona: Software developer"

- Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
/label ~"Persona: DevOps Engineer"

- Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney
/label ~"Persona: Systems Administrator"

- Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam
/label ~"Persona: Security Analyst"
-->

### Further details

<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->

### Proposal

<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->

### Documentation

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

### What does success look like, and how can we measure that?

<!-- 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. -->

### Links / references

/label ~feature
update issue template to encourage collaboration and metrics 2018-06-06 15:20:05 +00:00			`### Problem to solve`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 10:28:11 +00:00
Updates to Feature proposal.md 2019-01-17 21:17:54 +00:00			`<!-- What problem do we solve? -->`
Improve feature proposal template for improved product thinking 2018-12-10 15:23:18 +00:00
			`### Target audience`

Reword intro on target audience, and remove some line breaks to compress 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".`
Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00
Minor edit to personas mention 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)`
Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00
			`- Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: Product Manager"`

Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00			`- Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: Development Team Lead"`

Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00			`- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: Software developer"`
Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00
			`- Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: DevOps Engineer"`

Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00			`- Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: Systems Administrator"`

Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00			`- Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam`
Add slash commands 2019-01-23 19:24:03 +00:00			`/label ~"Persona: Security Analyst"`
Improve Target audience section for issue templates 2019-01-21 14:42:19 +00:00			`-->`
Improve feature proposal template for improved product thinking 2018-12-10 15:23:18 +00:00
update issue template to encourage collaboration and metrics 2018-06-06 15:20:05 +00:00			`### Further details`

Updates to Feature proposal.md 2019-01-17 21:17:54 +00:00			`<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->`
First pass for community issue templates * Include "Bug" template from the contribution guide * Include "Feature Proposal" template from the contribution guide 2016-08-23 10:28:11 +00:00
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 14:41:51 +00:00			`### Proposal`

Merge branch 'master' into 'template-improvements-for-documentation' # Conflicts: # .gitlab/issue_templates/Feature proposal.md 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 -->`
Improve feature proposal template for improved product thinking 2018-12-10 15:23:18 +00:00
Add documentation items to Feature Request issue template 2019-01-11 02:41:02 +00:00			`### Documentation`

Update Documentation section to include link to new Documentation Requirements section in docs 2019-02-08 18:18:47 +00: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 -->`
Add documentation items to Feature Request issue template 2019-01-11 02:41:02 +00:00
update issue template to encourage collaboration and metrics 2018-06-06 15:20:05 +00:00			`### What does success look like, and how can we measure that?`

Merge branch 'master' into 'template-improvements-for-documentation' # Conflicts: # .gitlab/issue_templates/Feature proposal.md 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. -->`
update issue template to encourage collaboration and metrics 2018-06-06 15:20:05 +00:00
Link to the issue templates in Contributing guide Change to use a better title style Add backticks to code segments Spelling and Grammar 2016-08-25 14:41:51 +00:00			`### Links / references`
documentation blurb in issue template 2017-03-17 11:43:32 +00:00
Adopt label renaming from ~"feature proposal" to just ~feature. 2019-01-14 18:18:05 +00:00			`/label ~feature`