For the complete documentation index, see llms.txt. This page is also available as Markdown.

Jira Notifications

Status Aging can keep alerts in the app or send Jira notifications.

Jira notification settings

Notification Modes

Mode
Description

In-app alerts only

Alerts stay in Status Aging. No Jira notification quota is used.

Limited direct Jira notifications

Sends issue notifications to selected recipients with budget limits.

Daily Jira digest

Sends one project digest per day with top overdue issues.

For a new rollout, start with In-app alerts only or Daily Jira digest. Move to direct notifications after the team agrees on alert rules.

Daily Jira Notification Budget

The daily budget limits how many Jira notifications Status Aging can send per day.

Set the budget to 0 to pause direct notifications.

Max Issues per Run

This limits how many issues can be included during each scheduled refresh.

For digest mode, it controls the maximum number of issues shown in the digest.

Subject Prefix

The subject prefix appears at the beginning of Jira notification subjects.

Example:

Recipients

Direct notifications can target:

  • Assignee.

  • Reporter.

  • Watchers.

  • Voters.

Only selected recipient groups receive notifications.

Include Flow Summary

When enabled, notifications include status aging context so recipients can understand the delay without opening the full report first.

Repeat While Overdue

When enabled, Status Aging can send repeated reminders while an issue remains overdue.

Use conservative intervals, such as:

Last updated