Exclude review-apps-broken issues from EP weekly report
Context
Same as !1949 (merged), but for the ~review-apps-broken label.
What does this MR do and why?
Exclude review-apps-broken issues from report
Those issues are transient, and resolved within a few hours in general. We do not need them in the weekly triage report.
Expected impact & dry-runs
Dry-run for policies/groups/gitlab-org/quality/ep-triage-report.yml
: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/4973932485
We had one review-app broken issue open at the time: gitlab-org/quality/engineering-productivity/review-apps-broken-incidents#602 (closed) (created_at
was set to 20h ago
at the time I ran the dry-run).
The issue is not part of the report
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(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
-
Edited by David Dieulivol