Announcement
|
FEATURE ANNOUNCEMENT

New Feature Announcement: Snooze - Unblock critical PR merges without losing track of risk

By
Anna Daugherty
May 27, 2026

Arnica Snooze gives developers a time-limited way to get past a blocked PR without permanently burying a real risk or handing admins a false sense of security.

Before Snooze, unblocking a PR meant a developer dismissed a real, sometimes critical severity finding to merge a critical fix. Marking these risks as “dismissed” ensured that nobody would return to fix it. It stayed buried in the backlog indefinitely. Security debt compounded silently.

Now, Snooze is a new finding status. Like a dismissal, but with an expiration date baked in.

  • Developer snoozes the finding. Using the same PR comment or ChatOps workflow they already know, a developer requests to snooze a finding. If "require review" is on for their role, the request routes to an approver first. Either way, the clock starts immediately at the moment of the request.
  • Finding temporarily unblocks. Once snoozed, the finding is temporarily dismissed. The PR status check is unblocked and the developer can merge. The finding is not gone, it’s time-stamped with an exact date and time it will reopen.
  • Auto-reopens to backlog. When the snooze period expires, Arnica automatically returns the finding to its open backlog state, exactly as it was before the snooze. No manual follow-up required. No one has to remember to go back to the finding and re-open it.
  • Configurable notifications. Admins configure who gets notified when a snoozed finding reopens: the original pusher, the product owner, or a specific recipient. The product owner mapping is the recommended default.

Configuration: New Dismissal Settings Tab

Snooze lives in a new dedicated tab in the Policies page, the first step toward simplifying how dismissal logic is organized in Arnica.

Setting Detail
Where to find it Policies > Dismissal Settings
Snooze duration Global — admin-set, applies to all snooze requests
Who controls the duration? Admins only — developers cannot choose ad hoc
Can I extend an existing snooze? No — duration is fixed at time of request
Snooze + No Capacity Mutually exclusive — enabling Snooze removes No Capacity
Require review for snooze requests? Optional — follows existing require-review policy per role
New findings view column Un-snooze date visible for all snoozed findings
Notification on reopen Configurable: pusher, product owner, product mapped, or named recipient

Important: Changing the global snooze duration does not extend snoozes already in progress. The duration is fixed at the moment a finding is snoozed. To extend, re-snooze the finding directly.

Snooze vs. No Capacity

Snooze replaces No Capacity. No Capacity was a permanent workaround with no return path. Snooze closes that gap.

BehaviorNo CapacitySnooze
Unblocks the PRYesYes
Finding auto-reopensNeverAlways
Duration admin-controlledNoYes — global policy
Audit trail with reopen dateNoYes
Notification on reopenNoConfigurable
Can co-exist with each otherNo — mutually exclusiveLive Now

Snooze works seamlessly with review requirements

Snooze seamlessly integrates with your existing policy rules, conforming to existing review requirements and prompting notification to your existing alert channels. No changes are needed to adopt the Snooze feature.

Snooze is Available Now

Snooze is live in production today.

Developers can now get unblocked without permanently compromising your risk data. Admins stay in control with global duration, require-review enforcement, and a full audit trail.

Get started in Policies > Dismissal Settings, view the documentation, or contact your Customer Success Rep for more info.

Reduce Risk and Accelerate Velocity

Integrate Arnica ChatOps with your development workflow to eliminate risks before they ever reach production.  

Try Arnica