SonarQube notification subscriptions lack digest, quiet-hours, and severity-threshold controls

Context

SonarQube notifies subscribers only when a Quality Gate status changes (e.g., OK to ERROR) and sends "New issues assigned to me" once per issue assignment. Users can subscribe or unsubscribe per project to specific notification types, but the platform does not provide built-in digest delivery, quiet-hours scheduling, or severity-threshold filtering.

Goal

Reduce alert noise for teams running frequent analyses across multiple projects while preserving visibility into meaningful Quality Gate transitions and new issue assignments.

Constraints and uncertainty

• Per-project subscription toggles are the only native noise-control mechanism.
• Webhooks fire on every analysis event and require external batching or filtering logic.
• Edition and version differences may affect which notification types exist and how they are labeled.

Questions

1. What patterns have teams adopted to implement digest or quiet-hours behavior on top of SonarQube's native subscriptions?
2. Can webhook payloads be reliably filtered by Quality Gate status change versus raw analysis events without parsing the full payload?
3. Are there documented API endpoints or admin settings in recent LTS releases that expose severity-level filtering for issue-assignment notifications?