kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Update Feature proposal template based on feedback

Browse source
This commit is contained in:
Mike Lewis 2019-01-23 05:43:03 +00:00
parent 04fea355d8
commit 4cbffdf8c8
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.gitlab/issue_templates/Feature proposal.md
View file

@ -4,7 +4,7 @@
### 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/research/personas or define a specific company role, e.g. "Release Manager" or "Security Analyst".
Use the persona labels as well https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A -->
### Further details
@ -18,7 +18,7 @@ Use the persona labels as well https://gitlab.com/groups/gitlab-org/-/labels?utf
### Documentation
<!-- What doc pages need to be created or updated across user, admin, and API docs?
What concepts, procedures, or information is needed in each area? Is there an 'old way' to deprecate in docs?
What concepts, procedures, or information is needed in each area? Is there an 'old way' that should be deprecated in the docs?
Product managers:
* By the kickoff, finalize the answers to the bullets above, and also: