Add documentation items to Feature Request issue template
This commit is contained in:
parent
89c4d2ae62
commit
43c82b2299
1 changed files with 8 additions and 1 deletions
|
@ -4,7 +4,8 @@
|
||||||
|
|
||||||
### Target audience
|
### Target audience
|
||||||
|
|
||||||
<!--- 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" -->
|
<!--- 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" -->
|
||||||
|
|
||||||
### Further details
|
### Further details
|
||||||
|
|
||||||
|
@ -14,6 +15,12 @@
|
||||||
|
|
||||||
<!--- 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 does success look like, and how can we measure that?
|
### 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 -->
|
||||||
|
|
Loading…
Reference in a new issue