> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/platform/ops/reports/ticket-cycle-time.md).

# 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="/files/YbzCWlVPhL3oIiwniRFo" 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="/files/cduSuPZCMcvjtagsHNDp" 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="/files/3PavWcUl1pmBg2sbEPIA" 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 %}