> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Example: Issue Fix Tracking

> An app that follows an issue from its first alert to its fix across every affected customer.

An [Issue](https://docs.resolve.ai/issues.md) groups the investigations that share one cause. When that problem spans alerts, code, pull requests, and feature flags, an app can put all of it on one page and keep it current until the Issue closes. This app follows a bug in ResolveAI from its first alert to its fix.

![Issue tracking app with a tree of causes, fixes, and pull requests on a timeline, internal names blurred](https://mintcdn.com/resolveai-0e94a547/jwX7TR61D9y-V7uy/images/apps/issue-fix-tracking.png?fit=max\&auto=format\&n=jwX7TR61D9y-V7uy\&q=85\&s=46eaff470d9dc06837df36258bcd3e6d)

## What it shows

* **Current state:** a summary of what was fixed, when, and where alerts still fire.
* **Key numbers:** linked alerts, affected customer organizations, alerts since the fix merged, and pull requests by status.
* **Timeline:** a tree of the cause, the code involved, the feature flags, and each pull request, placed on a timeline with markers for when the fix merged and when flags changed.
* **Time ranges:** the full history, the time since the fix merged, or the last seven days.

## Prompt

Asked in a chat about the Issue "Follow-up replies stall for minutes after an agent-team investigation concludes":

> Can you create me a tracker for fixes related to this issue

Resolve already had the Issue's context, including its linked investigations and [timeline](https://docs.resolve.ai/issues.md#follow-a-problem-through-the-fix), so the prompt didn't need to list the alerts, customers, pull requests, or flags.
