summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorDouwe Maan <douwe@gitlab.com>2018-06-15 08:01:48 +0000
committerDouwe Maan <douwe@gitlab.com>2018-06-15 08:01:48 +0000
commit6ce86d858a2d7bf21ed7a838149f13851362838a (patch)
tree1dcb9ea6a92d8e2a7e9e161f1316b072f9813a69 /CONTRIBUTING.md
parentfd34c9d6fe03b1dcd6698519dbe136dcc970e98e (diff)
parent8eed0071a1f13425bcad27b8791887c026c24dd2 (diff)
downloadgitlab-ce-6ce86d858a2d7bf21ed7a838149f13851362838a.tar.gz
Merge branch 'jr-design-artifact-process' into 'master'
Update process to create new design artifact issue See merge request gitlab-org/gitlab-ce!19465
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md15
1 files changed, 12 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ec904ada5bc..dcdf520ee6b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -306,14 +306,23 @@ 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 removes the ~"UX" label and 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 for that milestone, the
+Product Manager should create a separate issue for the ~"design artifact",
+assign the ~UX, ~"design artifact" and ~"Deliverable" labels, add a milestone
+and use a title that makes it clear that the scheduled issue is design only
+(e.g. `Design exploration for XYZ`).
+
+When the ~"design artifact" issue has been completed, the UXer removes the ~UX
+label, adds the ~"UX ready" label and closes the issue. This indicates the
+design artifact is complete. The UXer will also copy the designs to related
+issues for implementation in an upcoming milestone.
## Issue tracker