diff options
| author | Dimitrie Hoekstra <dimitrie@gitlab.com> | 2019-01-17 13:45:48 +0000 |
|---|---|---|
| committer | Phil Hughes <me@iamphill.com> | 2019-01-17 13:45:48 +0000 |
| commit | abc6394a753e11e800224ec53ca0f75e9cfa956f (patch) | |
| tree | 8f33be7114cae4e6036bf90da7dd4a3b6164d4c6 /.gitlab | |
| parent | c184407ee1df4d643235d6f6289b3bd2a3674861 (diff) | |
| download | gitlab-ce-abc6394a753e11e800224ec53ca0f75e9cfa956f.tar.gz | |
Update issue template with user journey, persona label additions, and clarification between success metrics and acceptance criteria
Diffstat (limited to '.gitlab')
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index a6f06998ef3..4d4d3bfda15 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -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/getting-started/personas or define a specific company role. e.a. "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 @@ -12,11 +12,11 @@ ### Proposal -<!--- How are we going to solve the problem? --> +<!--- How are we going to solve the problem? Try to include the user journey! --> ### 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 --> +<!--- Define both the success metrics and acceptance criteria. Note thet 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 |