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

# Quick Start

Use this sequence when setting up Status Aging for the first time in a project.

## 1. Open Status Aging

Open the Jira project and select **Status Aging**.

If this is the first run for the project, choose a baseline before scanning.

![First run baseline setup](/files/rhUn3IHVYsvOZuCSiaVg)

## 2. Choose a Baseline

For most existing projects, choose **Start fresh from today**.

This prevents old active issues from becoming overdue immediately because they existed before the app was installed.

## 3. Review the Project Dashboard

After setup, review the summary cards and overview charts.

![Project overview](/files/CiD2Ih81JCAlrmbNQrwV)

Look first at:

* Overdue count.
* At Risk count.
* Top bottleneck statuses.
* Needs attention list.

## 4. Filter the Issue Table

Use filters to narrow the table to the issues you want to discuss.

![Project filters](/files/OBkrc03gypzyCeG5QnVE)

Common filters:

* **Alert level**: Overdue.
* **Status**: Code Review, QA, Blocked, or Waiting for Client.
* **Assignee**: A specific user or Unassigned.
* **Search**: Issue key or summary text.

## 5. Open a Flow Report

Open the row action menu and select **Flow report**.

![Row actions menu](/files/cFLGgcGfWVO9pLHCXsH2)

The Flow report shows the lifecycle path, status history, bottleneck, and export actions.

![Flow report modal](/files/k02ynzXsXFbUwLzlRUxg)

## 6. Act on the Issue

Use the row actions or Flow report actions:

| Action          | Use when                                                   |
| --------------- | ---------------------------------------------------------- |
| **Add comment** | The issue needs a visible Jira update or owner response.   |
| **Snooze**      | The delay is known and should be checked again later.      |
| **Ignore**      | The issue should not be treated as a status aging problem. |
| **Restore**     | An ignored issue should be monitored again.                |

## 7. Tune Settings

Open **Settings** and adjust thresholds, scan scope, and notifications.

![Settings overview](/files/OSXqvRsyRSGVzFrgIbHs)