Filter alerts

A filter alert watches a whole ticket set instead of a single ticket. The scope is defined by a JQL query or a saved Jira filter: “any ticket in project X”, “all critical bugs”, “every request in my queue”.

Filter alerts are created on the HeadsUp overview page: Apps → HeadsUp → + New filter alert.

📷 Image to add

Screenshot, about 1600 px wide: the “New filter alert” dialog with a saved filter selected in the filter picker and the JQL field filled in. English UI.

Creating a filter alert

1. Choose the scope. The easiest way is the dropdown “Adopt saved filter”: it lists the user’s Jira filters and copies the JQL, which stays editable. Entering JQL directly works as well; it is validated on save.
2. Choose the trigger:
   • New ticket appears in the filter, for example every new bug in project X
   • Status change (any or a target status), new comment, priority change, assignee change
   • AI detects …, a plain-language condition evaluated across all tickets in the filter, see AI detection
   • SLA about to breach, see below
3. Optionally give it a name. The name appears in the email subject in square brackets, so the source of a notification is clear at a glance.

Filter alerts stay active permanently until deleted.

JQL is copied, not linked

The JQL of a saved filter is stored as a snapshot. Later changes to the saved Jira filter do not change the filter alert. To adopt changes, create the alert again.

Expiry date

Filter alerts always run permanently, so they can be given an expiry date. The field Expires offers No expiry, In 2 weeks, In 1 month, In 3 months, In 6 months or a specific date. No expiry is preselected.

This matters most for AI detection: a forgotten alert keeps consuming the shared AI quota of the site. An expiry date ends that without anyone having to remember.

Seven days before the date you get a reminder so you can extend it. An expired alert is paused, not deleted, and one click brings it back.

Note

For filter alerts the expiry notice arrives in the built-in inbox rather than by email. Jira’s notification API needs a ticket to send from, and a filter alert has no single ticket to anchor to.

SLA early warning (Advanced edition)

For Jira Service Management, a filter alert can warn before an SLA breaches: choose the trigger “SLA about to breach” and a threshold (1, 2, 4, 8 or 24 hours). HeadsUp checks open requests hourly and reports each request exactly once per alert, so an approaching breach does not turn into hourly spam.

This trigger is part of the Advanced edition. In the Standard edition it does not appear in the trigger list.

📷 Image to add

Screenshot, about 1200 px wide: the trigger dropdown with “SLA about to breach” selected and the threshold selector visible. English UI, Advanced edition.

Precision

Filter alerts on events (status, comment, priority, assignee, new ticket) react within seconds. The SLA check runs hourly; a warning can arrive up to about one hour after the remaining time falls below the threshold.