28-Jun-2026 — configure notification filter units ref #296

build 723 — commit 401d3be

What's new

Notification member filters can now use minutes, hours, days, weeks, months or years instead of being limited to month-based windows. Admins can also choose No date when they want the filter to ignore the date window entirely.

At a glance

• Notification configs now support a Filter Window Unit as well as an amount.
• The recipient pre-filter order now groups related member lifecycle options together.
• A new Added in last bulk load option selects members created by the latest bulk load.
• Email composer configs that skip the Events step now reliably send no events.

Where to find it

Open Admin -> Mail Settings, edit a notification configuration, and use the Member Selection plus Filter Window controls.

The unit dropdown appears for date-windowed member selections. Mailing List and Added in last bulk load do not show the window controls because those selections are not driven by a configurable date window.

How it behaves

The existing amount is still used, but the selected unit decides how far back the member filter looks. No date removes the date window entirely and hides the amount field.

A zero amount keeps date filtering behaviour but simplifies recipient labels to Added recently, Expired, and Missing from bulk load. Existing stored configs default to months so their behaviour stays unchanged until edited.

How to try it out

Set a notification config to Recently added or Expired members, choose a small unit such as minutes, and preview recipients in the email composer.

Use No date to remove the date window, or choose Added in last bulk load to target members created by the most recent bulk load.

Technical changes

• Extended notification config models and schema with timeUnit.
• Added minute and hour date units for notification filtering while keeping existing search range options intact.
• Added an idempotent Mongo migration to backfill missing timeUnit values to months.
• Updated member filtering, recipient labels, and config normalisation to honour the chosen unit.
• Guarded rendered event HTML and event inclusion state when the Events step is omitted.