> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/analytics-and-monitoring/dashboards/aging-dashboard.md).

# Aging Dashboard

The Aging Dashboard shows [Missions and Tickets](/missions/what-are-missions.md) that have been sitting on [boards](/mobile-app/your-mobile-boards.md) too long without being completed. A Mission is considered "aging" when it's been in Open or Claimed status for **more than 1 hour**.

***

## Why use the Aging Dashboard?

Without it, stuck Missions are invisible. A cleaning checklist that's been Open for 3 days looks the same as one posted 5 minutes ago — unless you have a tool that surfaces the difference. The Aging Dashboard answers: "Where is work getting stuck, and for how long?"

**Example:** A maintenance audit has been on the board for 7 days. Nobody noticed because new Missions keep appearing above it. The Aging Dashboard highlights it immediately in the ">7D" column.

***

## How to use it

Go to **Dashboard → Aging**. Two tabs:

### Unit tab (Missions)

1. Select a **Unit** (one at a time)
2. Select a **date** (defaults to today — single date only, no ranges)
3. See aging Missions grouped by time: 1–3h, 3–6h, 6–12h, 12–24h, 1–2D, 2–3D, 3–5D, 5–7D, >7D

At the top, daily statistics show: **Posted** (new + existing), **Closed**, **Canceled**, **Bounced**, and **Tickets triggered** — all for the selected date.

### Ticket Board tab (Tickets)

1. Select a **Ticket Board** (Unit or Organization — one at a time)
2. Same time groupings and date selection
3. Statistics show: **Posted**, **Closed**, **Bounced**, and **New Tickets**

***

## Good to know

* Shows a **snapshot of one day** — date ranges are not supported
* Aging thresholds are fixed (1 hour minimum) and cannot be customized
* Once a Mission is Closed or Canceled, it's no longer considered aging
* Web only — not available on mobile


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.taskmaverick.com/analytics-and-monitoring/dashboards/aging-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.