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

# Recommended Workflows

## Daily Team Review

1. Open the Jira project.
2. Go to **Status Aging**.
3. Check **Overdue** and **At Risk** counts.
4. Filter by **Overdue**.
5. Review the longest status age items first.
6. Open **Flow report** for unclear cases.
7. Add comments or assign follow-up work.
8. Snooze known delays.
9. Ignore issues that should not be monitored.

## Standup Workflow

1. Open **Status Aging**.
2. Filter to **Overdue**.
3. Sort by **Status age**.
4. Discuss the top stuck issues.
5. Decide whether to move forward, reassign, comment, snooze, or ignore.

## Flow Improvement Review

1. Open **Status Aging**.
2. Review bottleneck statuses and health distribution.
3. Open several Flow reports.
4. Look for repeated long stays in the same status.
5. Adjust thresholds if needed.
6. Improve the team workflow around bottleneck statuses.

## Notification Rollout

1. Start with **In-app alerts only**.
2. Tune thresholds until the dashboard is useful.
3. Move to **Daily Jira digest** for low-noise team visibility.
4. Enable **Limited direct Jira notifications** only for teams that want direct issue-level alerts.