> For the complete documentation index, see [llms.txt](https://apps.embed-in.com/status-aging-alerts-time-in-status/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apps.embed-in.com/status-aging-alerts-time-in-status/project-settings.md).

# Project Settings

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

![Settings overview](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-3e7c273bf9f9b79c1648a15a460f158b5488da49%2F10-settings-overview-baseline.png?alt=media)

## Baseline Mode

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

See [First Run Baseline](/status-aging-alerts-time-in-status/first-run-baseline.md) for the full explanation.

## Scan Scope

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

![Scan scope settings](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-77991ac0df00b82ddc05e4a9ac62b7756bd9b8a6%2F11-settings-scan-scope.png?alt=media)

| 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](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-33f9fe80f72e507eeb9e2a28a25e6dcbbb10feaa%2F12-settings-threshold-rules.png?alt=media)

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:

```
At-risk starts at 70% of the threshold
```

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](/status-aging-alerts-time-in-status/jira-notifications.md) for details.