From 9e2b98336a28fb307483faf4d9b27edbf01baaf7 Mon Sep 17 00:00:00 2001 From: Mo Zhu Date: Fri, 18 Nov 2022 08:17:46 -0800 Subject: [PATCH] Reminder to update the transparency page for new features (#8761) --- .github/ISSUE_TEMPLATE/new-feature-work.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/new-feature-work.md b/.github/ISSUE_TEMPLATE/new-feature-work.md index 71d9543040..08d7a9b419 100644 --- a/.github/ISSUE_TEMPLATE/new-feature-work.md +++ b/.github/ISSUE_TEMPLATE/new-feature-work.md @@ -42,6 +42,7 @@ TODO - **Documentation** Do you want a guide written about this? What things/aspects should we make sure is covered by the documentation? +- **Transparency** Do we need to update the transparency guide to reflect new functionality? - **Analytics** How are we going to measure usage and success? Make sure engineering knows these need to be built. - **QA** Any special QA notes? - **Other depts.** Should other Fleet departments such as marketing, sales, CX be informed after this is shipped?