Skip to content

Recurring: On-call & Incident support work (Sprint 8) #3460

Description

@amazingphilippe

About

This is a new recurring task we can use to help make on-call and incident support (New-starting Sprint 8) work visible (see parent-feature description for more context on this). Those involved in the on-call an/or incident support work can add and remove themselves and modify this ticket accordingly.

Recurring checklist for this task

  • Dependency bumps
  • Monitor ops channels for alarms
  • (add other as needed/relevant)

5 Incidents happened or are happening this sprint (August 26-Sept.15), implicating one or more App team members:

  • incident-2026-08-26-short-code-failed-audit
  • incident-2026-08-27-bc-parks-notifications-listing-is-having-a-fit
  • incident-2026-08-31-wichtel-access-ised-from-austria
  • incident-2026-09-02-emails-too-large-for-sqs-queue
  • incident-2026-09-03-bell-ip-address-triggers-sentinel-alarm

Other things that came up this sprint

  • [ ]

Recurring checklist for closing this task

  • update any above as done or N/A
  • create new tasks under this parent feature (or a different parent if that is a better fit) to represent new work emerging from on-call and incident support this sprint
  • make a duplicate of this card, remove any information that was unique to this sprint only, and put the card in the relevant parent feature (DM can do this too)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

DevTask for implementation of a technical solution

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions