Skip to content

Update tests to select best group to assign master broken incidents

What does this MR do and why?

Describe in detail what your merge request does and why.

Update tests to select the best group to assign master broken incidents

Follow-up on gitlab-org/quality/engineering-productivity/team#215 (comment 1436690358)

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Action items

Merge request reports