From 34a125f380fbe7374eb017debd3239c10456a10f Mon Sep 17 00:00:00 2001 From: James Ramsay Date: Wed, 6 Jun 2018 01:53:41 +0000 Subject: [PATCH 1/4] Update process to create new design artifact issue --- CONTRIBUTING.md | 9 ++++++--- 1 file 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 From 1a271281143d42a91bd70f50900177fa5a1af3e2 Mon Sep 17 00:00:00 2001 From: James Ramsay Date: Thu, 14 Jun 2018 13:46:45 +0000 Subject: [PATCH 2/4] Increase detail --- CONTRIBUTING.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2309743612c..aa39b5683a4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -312,11 +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. -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`). +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`). -Once the ~"design artifact" issue has been completed, the UXer removes the ~"design artifact" label and applies the ~"UX ready" label. +When the ~"design artifact" issue has been completed, the UXer removes the ~UX +and ~"design artifact" labels, 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 From d16256bfb9ddf7e9efe887ff7245a61ee2e10973 Mon Sep 17 00:00:00 2001 From: James Ramsay Date: Thu, 14 Jun 2018 19:25:14 +0000 Subject: [PATCH 3/4] Fix design artifact should not be removed --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index aa39b5683a4..b5231ba5c62 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -320,9 +320,9 @@ 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 -and ~"design artifact" labels, 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. +labels, 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 From 8eed0071a1f13425bcad27b8791887c026c24dd2 Mon Sep 17 00:00:00 2001 From: Sarrah Vesselov Date: Thu, 14 Jun 2018 19:29:16 +0000 Subject: [PATCH 4/4] remove plural from 'label' --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b5231ba5c62..32635b9012d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -320,7 +320,7 @@ 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 -labels, adds the ~"UX ready" label and closes the issue. This indicates the +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.