Summary: Statuspal should send a dedicated subscriber notification whenever the severity of an ongoing incident is changed (e.g., downgraded from Major to Minor or upgraded from Minor to Major), ideally with a mandatory reason explaining the change. Current behavior: When the severity of an incident is changed during its lifecycle, no notification is triggered by the severity change itself. Subscribers only see the new severity implicitly in the subject line of subsequent updates. Example: Initial notification: "Major Incident Update: Sporadic Login Issues with Web, Mobile and Desktop Apps" The incident is internally downgraded to Minor, without any communication to subscribers Follow-up notifications suddenly read: "Minor Incident Update: Sporadic Login Issues with Web, Mobile and Desktop Apps" From the subscriber's perspective, the incident silently changed from Major to Minor. This is confusing and can look like an inconsistency rather than a deliberate reassessment. Expected behavior / Proposed solution: When the severity of an open incident is changed, Statuspal triggers an explicit notification, e.g. "Incident severity changed: Major → Minor", including a mandatory reason field so subscribers understand why the incident was reassessed (e.g., "Impact reduced to a small subset of users; core functionality restored"). Optionally, this could be configurable per status page (enable/disable, or only for upgrades/downgrades). Why this matters: Transparency across the full incident lifecycle, consistency of follow-up messages, and trust — proactively communicating a downgrade with a reason signals the situation is under control instead of looking like the incident was quietly relabeled. Additional context: Severity distinctions already exist in Statuspal (including in custom configurations), but there is currently no automatism that triggers a notification based on a severity change. This request would close that gap.
