Avoid reassigning issues for verification
What does this MR do and why?
Currently, vacant Issues of the Security Policies/Threat Insights group labelled with workflowverification are assigned a random group member. This suffers from the problem where someone unassigns themselves from an Issue, and gets immediately reassigned to the Issue by the bot due to bad luck.
This MR avoids this by determing the most recently unassigned username, and excluding it from the random sample.
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-with-a-dry-run on how to perform dry-runs.
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
-
Edited by Dominic Bauer