You need to sign in or sign up before continuing.
Draft: Close issues labelled with 'auto closed' label
requested to merge 922-close-issues-that-have-the-auto-closed-label-but-are-not-actually-closed into master
What does this MR do and why?
This one-off policy would close issues in the gitlab-org/customers-gitlab-com and gitlab-org/license-gitlab-com projects that have the auto closed label and should have been closed for a long time already.
Expected impact & dry-runs
| Project | Expected count of closed issues (including security & ~vulnerability) | Expected count of closed issues (excluding security & ~vulnerability) |
|---|---|---|
gitlab-org/customers-gitlab-com |
241 | 185 |
gitlab-org/license-gitlab-com |
14 | 9 |
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group=> -
Relevant Slack channels => -
Engineering week-in-review
-
Closes #922 (closed).
Edited by Rémy Coutable