QTest notification subscriptions lack digest batching and quiet hours

Goal is to keep operational alerts useful without notification noise in QTest.

QTest offers per-user notification subscriptions for project events such as test runs, requirements changes and defects. Controls are managed through user profile and project subscription settings with opt-in per object type and role. Delivery is limited to objects the user can access.

There is no documented native support for quiet hours, digest batching or frequency throttling in the core product. Behavior can vary by edition and deployment. Alert relevance therefore depends on project membership, role permissions and manual subscription hygiene.

Decision point is whether to rely on native subscriptions for operational alerts or route critical alerts through an external integration to gain control over noise, batching and escalation.

Is native subscription support available for digest batching, quiet hours or frequency throttling for email alerts?

What is the effect of project membership and role permissions on cross-project alert visibility?

Is external integration required to control frequency and escalation of critical alerts?