QTest notification subscriptions lack digest batching and quiet hours

Answer the exact question first

Is native subscription support available for digest batching, quiet hours or frequency throttling for email alerts? No. QTest’s core product does not provide any UI or API parameters to batch notifications, schedule delivery windows, or throttle the frequency of email alerts. Each enabled event type is sent to the user immediately after the event occurs.

Effect of project membership and role permissions on cross‑project alert visibility

Alert visibility is strictly scoped to the projects a user is a member of and the roles that grant access to specific object types. If a user is not a member of a project, they will never receive notifications from that project, regardless of the subscription settings in other projects. Even within a project, a user’s role determines which event categories they can subscribe to; for example, a “Tester” role may receive defect updates, while a “Reporter” role may not.

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

Because the native system cannot batch or delay notifications, any requirement for quiet hours, digest emails, or escalation thresholds must be handled outside of QTest. Typical approaches include:

• Routing all QTest emails to a dedicated mailbox and using an email client rule or server‑side filter to group or postpone messages.
• Using QTest’s REST API (e.g., GET /api/v1/events) to poll for changes and then sending aggregated alerts through a custom script or a third‑party service such as Slack, Teams, or a ticketing system.
• Leveraging existing integrations that already provide batching or quiet‑hour features (e.g., a Jira‑to‑Slack bridge that can be configured to send a daily digest).

Concrete steps to verify the current behavior in your instance

1. UI verification
   • Log into QTest as an administrator.
   • Navigate to My Settings > Notifications.
   • Check that each event type (Test Run, Requirement Change, Defect, etc.) has a simple toggle but no options for scheduling, batching, or quiet hours.
2. API verification
   • Make a GET request to /api/v1/notifications (or the equivalent endpoint for your QTest edition).
   • Inspect the JSON payload; confirm that no fields such as digestFrequency, quietHoursStart, or throttleLimit are present.
3. Attempt to create a new subscription rule
   • From the Notifications page, click “Create New Subscription”.
   • Verify that the form only asks for event type and target (email, Slack, etc.) and does not offer scheduling or batching options.
   • If any such options appear, note the exact QTest version and report back.

Missing diagnostic detail that could change the recommendation

Do you currently use a custom notification plugin or a third‑party integration (e.g., a Slack or Teams connector) that already implements digest or quiet‑hour logic? If so, that integration might obviate the need for an additional external workflow.