Bug rota

To prevent unecessary context-switching, the engineering team implement a "bug rota". This involves one engineer monitoring error reports for the agreed period, and a handover session where gathered issues are triaged, and the rota is passed to the next engineer.

Process

Daily workflow

• As part of their daily routine, the engineer on bug watch keeps an eye on the #bot-bugsnag, #bot-third-party-incidents and #engineering-alerts channels
• Other engineers should avoid digging into these alerts, unless they know they will have caused something on a review app or staging. If so, leave a comment for the engineer on bug watch
• The engineer on bug watch should log any reports of value in the Bug Rota document in Notion, along with some initial triage
• If the alert looks severe refer to the incident management guide

Handover

• In the handover session the Bug Rota document for the previous period should be reviewed
• Actions should be added to the Platform Backlog or Product Kanban Board depending on their severity and how much they directly impact the customer experience
• It's OK for there to be no action on a report – we can't (and shouldn't) fix everything
• The bug watch passes to the next engineer in the list. Ensure this doesn't coincide with periods of expected absence, and if it does, choose a suitable alternative.