# Ticket Cycle Time

Ticket Cycle Time measures the average time it takes for a ticket to move from the "In Progress" status to the "Done" status. It is a key metric in DevOps that represents the efficiency of your engineering workflow and the speed of your delivery.

<figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FmwYHVASA09blCDlS05NL%2FScreenshot%202025-09-08%20at%205.08.20%E2%80%AFPM.png?alt=media&#x26;token=250c9f34-a476-464c-8768-4d4fde312b5b" alt=""><figcaption></figcaption></figure>

### How Typo Calculates Ticket Cycle Time

#### **1. Data Sources**

Typo gathers data from your integrated tools to provide an accurate and comprehensive view of your team's cycle time.

* Issue Tracker (e.g., Jira, Linear): Provides critical data on issue types, status history, and timestamps.
* Custom Fields: Allows for filtering and analysis based on custom categories (e.g., "Developer," "Team name").

#### **2. Calculation Logic**

Typo calculates the time from the moment a ticket enters the "In Progress" state until it is marked as "Done".&#x20;

### Cycle Time View in Typo

Typo’s dashboard provides a granular, visual representation of your team's cycle time, allowing you to track trends and identify bottlenecks.

**1. Cycle Time**

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2F7ZzwcOZA3WXGDL4kZ1jW%2FScreenshot%202025-09-08%20at%203.35.45%E2%80%AFPM.png?alt=media&#x26;token=932b096f-f4f3-4a7c-a7f8-afbf7c6cc721" alt="" width="563"><figcaption></figcaption></figure></div>

Overall Cycle Time: Displays the average cycle time for all completed tickets in the selected date range along with the count of tickets.

2. **Cycle Time States:**&#x20;

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FImSNd5J0ZRlMrfSg9Ihq%2FScreenshot%202025-09-08%20at%203.48.47%E2%80%AFPM.png?alt=media&#x26;token=5af11913-9369-4da6-a5f1-f1150bf5a53f" alt="" width="563"><figcaption></figcaption></figure></div>

Shows the current status of all the tickets in the selected project & date range. along with the Visualization of the average time spent in each stage (e.g., Coding, Review, Merge).

**2. Completed Tickets Table**

The table provides a detailed, searchable view of every completed ticket, including:

* Title
* Issue Type
* Developer
* Cycle Time
* Start Date (first moved to "In Progress")
* End Date (first moved to "Done")
* Linked PRs
* Status

### How to Use This Data

By analyzing your Issue Cycle Time and its sub-stages, you can:

* Identify Bottlenecks: Pinpoint specific stages where tickets are getting stuck.
* Optimize Workflow: Make data-driven decisions to improve your team's efficiency.
* Improve Planning: Use historical data to create more accurate estimates for future projects.
* Communicate Effectively: Share a clear, visual representation of your team's delivery performance with stakeholders.

{% hint style="info" %}
To enable this report for your account, please reachout to support or <hello@typoapp.io>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://typo.gitbook.io/typo-help-docs/platform/reports/ticket-cycle-time.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.