summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorJames Ramsay <jramsay@gitlab.com>2018-06-06 01:53:41 +0000
committerJames Ramsay <jramsay@gitlab.com>2018-06-06 01:53:41 +0000
commit34a125f380fbe7374eb017debd3239c10456a10f (patch)
tree47548a4ed0a79fb2076cb5190e0ff055a23c2399 /CONTRIBUTING.md
parent610a8f2497a040087396a224697b8b3aad66664c (diff)
downloadgitlab-ce-34a125f380fbe7374eb017debd3239c10456a10f.tar.gz
Update process to create new design artifact issue
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 295f9bca24b..2309743612c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -306,14 +306,17 @@ To better understand the priority by which UX tackles issues, see the [UX sectio
Once an issue has been worked on and is ready for development, a UXer applies the ~"UX ready" label to that issue.
The UX team has a special type label called ~"design artifact". This label indicates that the final output
-for an issue is a UX solution/design. The solution will be developed by frontend and/or backend in a subsequent milestone.
+for an issue is a UX solution/design. The solution will be developed by frontend and/or backend in a subsequent milestone.
Any issue labeled ~"design artifact" should not also be labeled ~"frontend" or ~"backend" since no development is
needed until the solution has been decided.
~"design artifact" issues are like any other issue and should contain a milestone label, ~"Deliverable" or ~"Stretch", when scheduled in the current milestone.
-Once the ~"design artifact" issue has been completed, the UXer removes the ~"design artifact" label and applies the ~"UX ready" label. The Product Manager can use the
-existing issue or decide to create a whole new issue for the purpose of development.
+To prevent the misunderstanding that a feature will be be delivered in the assigned milestone, when only UX design is
+planned, the Product Manager should create an issue specifically for the ~"design artifact" with a title that makes
+this clear (e.g. `Design exploration for XYZ`).
+
+Once the ~"design artifact" issue has been completed, the UXer removes the ~"design artifact" label and applies the ~"UX ready" label.
## Issue tracker