## Problem Statement We have over 300 open issues in [gitlab-org/gitlab](https://gitlab.com/gitlab-org/gitlab/-/issues?scope=all&state=opened&label_name[]=devops%3A%3Asecure&label_name[]=frontend&not[label_name][]=group%3A%3Athreat%20insights ) assigned to ~"devops::secure" ~frontend (and not ~"group::threat insights"). 230 are over a year old. Problems this creates: 1. It's difficult to use the current list to find work. 1. A lot of older issues are no longer relevant or are significantly out of date. 1. Though our team does regularly refinement, it's been difficult to make significant progress in keeping the backlog tidy. Therefore we plan to allocate capacity in %14.4 to declutter and polish our backlog. ## Goals 1. Default to closing issues. We don't want to be in analysis paralysis. The important topics will resurface and can be easily reopened if there is interest or demand. 1. Distributed workload across our team. We want to avoid having any declutter heroics. 1. Be transparent in this activity. ## Issue assessment parameters 1. Is the request still relevant? 1. Is this valuable to the user? 1. Was it already fixed or partially fixed? Was the partial fix "good enough"? 1. What kind of activity has occurred? Who is in notifications list? (issues that were created with no follow up are probably low value) 1. How old is the issue 1. Is the complexity vs. value worth it? 1. Is this work blocked by something? Jannik: “block factor” 1. What is the time to unblock? 1. Is that work scheduled? 1. Does the work include backend? 1. Is it waiting on a dependency like GitLab UI? 1. Is this better for Threat Insights? 1. Can this be open to community contributors? ## Issue actions to take 1. Close it? 1. Schedule it? 1. Refine it? 1. Move it to another group? 1. For issues we are keeping open, follow our standard refinement steps at https://about.gitlab.com/handbook/engineering/development/secure/workflow/ Use this handy template to close an issue. ``` /close Closing this issue per our clean up initiative at https://gitlab.com/groups/gitlab-org/-/epics/6732 . Please coordinate with the [group PM](https://about.gitlab.com/handbook/product/categories/) if you wish to reopen and prioritize. ``` ### For Composition Analysis Issues 1. For ~"group::composition analysis" issues with no activity, please use this comment template to reassign the epic and close. ``` /epic &4488 /close This issue is not on the 12 month plan, no recent activity, but can reopen if interest picks back up. Mention CA group PM to get attention https://about.gitlab.com/handbook/product/categories/#composition-analysis-group ``` ## Preparation / Milestone set up - [ ] Close issues older September 1st, 2020 that are in the backlog. - [ ] Export issue list and import into Google sheet - Worksheet at https://docs.google.com/spreadsheets/d/1MHPWDNpSF0t-W2n2GyjO3vYbRx3waLdj-j4hgvWsteA/edit?usp=sharing - [ ] Divide equally across the team ## Resources 1. [Refinement meeting agenda doc where this was discussed](https://docs.google.com/document/d/1TSX1nDk4DpiN642ZS8iJSzdppfF0IdMEGIvMl6XW3d4/edit#bookmark=id.gsapxphh08qd) 1.