Automating ticket triaging for Arti
During today's Arti meeting, the team expressed interest in having daily triaging happening of tpo/core/arti. I think that's a fine idea.
How about we do the following:
- When a new ticket comes in, our @triage-bot does the following:
- assigns the ticket to a random, non-busy (as in Gitlab's busy flag that people should use when going away for longer periods of time) team member and
- marks the ticket with the label "Triage"
- The assigned person takes a look at it and decides on whether the issue can:
- be resolved right away or
- be reassigned to someone else or
- be closed as duplicate/invalid/etc or
- Additionally, the assigned person is also responsible for marking the non-closed tickets with the proper labels that we use (Icebox, Backlog, etc.)
The bot will ignore tickets that have the usual "triaged tickets" labels: Icebox, Roadmap::Future, Backlog, Next, Doing, and of course ignore tickets with the label ~Triage.
@eta @Diziet @nickm Let me know what you all think and I'll make it happen. Additional suggestions welcome.
We can later extend the system to also re-assign tickets that have been marked with Triage as label, but had no activity for 7 days to handle the case where a person may go AFK without marking themselves as busy in Gitlab.