> 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](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-cb32cdd2e91fd0d3064d95f641018451627a0255%2F01-first-run-baseline-setup.png?alt=media)

## 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](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-fbbffcce867259d99a08ade248871e934b68c5e1%2F02-project-overview.png?alt=media)

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](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-f9e508317d8ec4e537433bbd58f1791442e87c2f%2F03-project-filters.png?alt=media)

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](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-744668aa0da808aabd6b7e7e773b8762e7c5b5d1%2F06-row-actions-menu.png?alt=media)

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

![Flow report modal](https://3944060571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft8iV5fsdAVKU05SVXh33%2Fuploads%2Fgit-blob-cfa0fc93fc814a1e51a674efa45389c9ceb5f3e8%2F07-flow-report-modal.png?alt=media)

## 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](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)