# Issue Age

**Issue Age** is a key metric that provides insight into how long it takes for a team to resolve a ticket or issue, from its creation to its completion. Understanding and optimizing Issue Age is crucial for maintaining a high level of productivity and ensuring customer satisfaction.

{% hint style="info" %}
**Formula:**

Issue Age = Completion Date - Creation Date
{% endhint %}

<figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2F26TpaG3A28JGzusr7JGE%2Fimage.png?alt=media&#x26;token=0fcdc105-d627-4405-afd7-c6abe29f1cc2" alt="" width="563"><figcaption></figcaption></figure>

#### **Example**:

* **Creation Date**: August 1, 2024
* **Completion Date**: August 5, 2024
* **Issue Age**: 4 days

#### Why Is Issue Age Important?

Issue Age is a critical metric for several reasons:

* **Team Efficiency**: A lower Issue Age indicates that your team is resolving issues quickly, which is a sign of efficiency. A higher Issue Age might suggest bottlenecks or delays in the workflow that need to be addressed.
* **Customer Satisfaction**: For customer-facing teams, reducing Issue Age is essential. Faster resolution times lead to higher customer satisfaction and a better overall experience.