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

Project Settings

Settings are project-specific. Open them from the Status Aging project page.

Settings overview

Baseline Mode

Baseline mode controls how Status Aging treats issues that existed before setup.

See First Run Baseline for the full explanation.

Scan Scope

Scan scope controls which active issues and workflow statuses are included.

Scan scope settings
Setting
Description

Default status limit

Default threshold used when a status has no custom rule.

Max active issues to scan

Maximum active issues scanned for the project. The current beta maximum is 200.

Skip Jira Done category

Excludes completed work from active status aging checks.

Statuses to ignore

Comma-separated Jira status names that should not trigger status aging alerts.

Status Thresholds

Use status thresholds to override the default limit for specific statuses.

Status threshold rules

Example setup:

Status
Overdue after

Code Review

24h

QA

48h

Blocked

24h

Waiting for Client

120h

Each rule can be enabled, disabled, removed, or edited.

At-Risk Timing

At-risk timing controls when an issue becomes At Risk before it becomes Overdue.

Example:

If the threshold is 10 hours:

Time in status
Health

0h-6h 59m

On Track

7h-9h 59m

At Risk

10h+

Overdue

Jira Notifications

Jira notification settings control whether alerts stay in-app, go out as limited direct notifications, or arrive as a daily digest.

See Jira Notifications for details.

Last updated