Commit 6ce86d85 authored by Douwe Maan's avatar Douwe Maan

Merge branch 'jr-design-artifact-process' into 'master'

Update process to create new design artifact issue

See merge request gitlab-org/gitlab-ce!19465
parents fd34c9d6 8eed0071
...@@ -312,8 +312,17 @@ needed until the solution has been decided. ...@@ -312,8 +312,17 @@ 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. ~"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 To prevent the misunderstanding that a feature will be be delivered in the
existing issue or decide to create a whole new issue for the purpose of development. 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 ## Issue tracker
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment