> 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/gitbook.md).

# Overview

Status Aging Alerts for Jira helps teams find Jira work items that stay too long in one workflow status.

The app answers three operational questions:

* Which active issues are getting stuck?
* Where are they getting stuck?
* Who should act before the delay becomes invisible?

![Project overview](/files/CiD2Ih81JCAlrmbNQrwV)

## What the App Adds to Jira

Status Aging adds these Jira views and fields:

| Area                             | What it provides                                                                 |
| -------------------------------- | -------------------------------------------------------------------------------- |
| **Status Aging project page**    | Project-level dashboard, filters, stuck issue table, flow reports, and settings. |
| **Status Age issue panel**       | Issue-level status age, lifecycle path, status history, and alert actions.       |
| **Read-only Jira custom fields** | Health, current status age hours, and hours over threshold.                      |
| **Scheduled refresh**            | Hourly refresh for projects that have opened or configured the app.              |

## Health Labels

The app classifies every scanned active issue with one health label.

| Label        | Meaning                                                   |
| ------------ | --------------------------------------------------------- |
| **On Track** | The issue is still within the configured threshold.       |
| **At Risk**  | The issue is close to the threshold.                      |
| **Overdue**  | The issue has exceeded the threshold.                     |
| **Snoozed**  | The alert is temporarily hidden until the snooze expires. |
| **Ignored**  | The alert is hidden until someone restores it.            |

## Core Concepts

**Status age** is the time an issue has spent in its current Jira workflow status.

**Threshold** is the allowed time for a status. For example, Code Review may be overdue after 24 hours, while Waiting for Client may be overdue after 5 days.

**Lifecycle path** shows how the issue moved through statuses and how long it spent in each status.

**Bottleneck** is the non-completed status where an issue spent the most time.

## Who Should Use It

Status Aging is useful for:

* Scrum masters and delivery leads running daily triage.
* Engineering managers monitoring blocked or stale work.
* QA and release teams watching Review, QA, and Ready for Release queues.
* Support and operations teams tracking customer-facing delays.