| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Metric
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
The main condition for calculating the Cycle and Lead Time is that the issue should have the “Done” (you can customize which statuses to count as “Done” - read more here) status at least once during the selected Time frame. |
Cycle Time
The Cycle Time metric measures the duration from when work starts (issue moved to the “In Progress” status category) to when it’s completed (issue moved to the “Done” status category).
You can customize which statuses to count as “In progress” - read more here.
You can customize which statuses to count as “Done” - read more here.
Lead Time
The Lead Time metric tracks the
...
time from when an issue is created to when it’s finished (the issue is moved to the “Done” status category).
...
Issue state
Define the issue state you want to include in the chart builduing.
...
Cycle Time chart
...
Time in Status chart
...
Trend chart
...
Done
...
Includes only issues that have reached the 'Done' state within the selected interval, calculating the time taken to complete these tasks.
...
Includes only issues that have reached the 'Done' state, calculating the time they spent in each status before completion.
...
Tracks trends for issues that reached the 'Done' state within the selected interval, helping predict future performance based on completion times.
...
Updated
...
Includes issues that have undergone any status change during the selected interval, calculating the time from when they were first updated to when they are completed.
...
Includes issues that have undergone any status change, calculating the time spent in each status during the selected interval.
...
Shows trends for issues that have undergone any status change, reflecting changes in workflow dynamics over time.
...
Created
...
Includes only issues that were created within the selected interval, tracking their Cycle or Lead time from work starts/creation to completion.
...
Includes only issues that were created within the selected interval, tracking the time they spent in each status until they moved to the next phase.
...
Displays trends for issues that were created within the selected interval, providing insights into how long tasks take from creation to completion.
...
Any
...
Includes all issues, regardless of their status, ensuring a comprehensive calculation of Cycle/Lead time across the selected interval.
...
Includes all issues in the selected interval, calculating the time spent in each status across the entire workflow.
...
You can customize which statuses to count as “Done” - read more here.
Absent metric
If there was no transition from “In Progress” to “Done” status within the specified period, the issue will be present in the Issue list, but the Cycle/Lead Time will not be calculated for such an issue.
It allows to align the issues scope between the Histogram Cycle Time and Time in Status Cycle Time Charts as the issue will have the “In Progress” statistic but have not the Cycle or Lead Time metric.
| Expand | ||
|---|---|---|
| ||
Imagine, that the issue was reopened during the same Time frame. The issue was moved through the "In Progress" and "Done" statuses (default or custom) and at the end of the selected Time frame it is remains not "Done". In this case, the Cycle/Lead Time metric calculates part of the workflow till the status “Done”. Set the Timer control to specify when to pause the calculation:  |
Exception: the “Metric” selection is unavailable for the Time in Status Cycle Time Chart because this chart focuses solely on the time tasks spent in each status rather than tracking the overall cycle or lead time. The goal is to analyze where tasks are held up within the workflow, not to measure the total duration from start to finish.
The option is available for the Cycle Time Histogram and Cycle Time Trend Charts.
In Progress statuses
The In Progress Statuses option allows you to customize which statuses are considered "In Progress" for all your charts, whether it's Cycle Time Histogram, Time in Status Cycle Time, or Cycle Time Trend Charts.
This flexibility lets you redefine what "In Progress" means for your workflow by including statuses that are typically categorized as "To Do" or "Done".
Sometimes, your team might have specific statuses that don’t fit neatly into the default "In Progress" category but are crucial to your workflow. For example, you might have a "To Do" status like "Design Approved" or a "Done" status like "Ready for Release". By selecting these as "In Progress," you can ensure that the time spent in these critical stages is accurately tracked and analyzed.
...
By default, all statuses of the “In Progress” status category are predefined.
Exception: when the “Lead Time” metric is selected, the “In Progress” field disappears for the Cycle Time Histogram and Cycle Time Trend Charts because for the Lead Time the progress between the date of creation and completion is not important.
Done statuses
The Done Statuses option allows you to customize which statuses are considered "Done"
...
. This flexibility lets you redefine what "Done" means for your workflow by including statuses that are typically categorized as "In Progress" or even "To Do".
In some workflows, the completion point might not align with the traditional "Done" category. For example, your team might have an "In Progress" status like "Ready for Release" or a "To Do" status like "Final Review" that marks the end of their process. By selecting these statuses as "Done", you can ensure that your charts accurately reflect when work is truly finished.
Exception: the Done Statuses option is not available for the Time in Status chart because this chart’s primary focus is to track how long tasks are spent in each individual status - no matter their category, rather than when they are completed. The goal of the Time in Status chart is to provide insights into the time distribution across all statuses within the workflow, making the concept of a "Done" status unnecessary for this specific analysis.
Start timer on
Pause timer on
By default, charts take all statuses from the “Done” status category.
| Expand | ||
|---|---|---|
| ||
Imagine your team includes Developers Team and QA Team with the following statuses of the workflow.  For the Developers Team, work starts from “In Progress”, passes the “In Code Review” status, and can be considered “Completed” when the issue moves to “Ready for QA” status. The setting of the fields will look like this:  For the QA Team, work starts from the “Ready for Test” status, passes the “In Testing” status, and can be considered “Completed” when the issue moves to the “Done” status. The setting of the fields will look like this:  |
Timer control
The Start timer on and Pause timer on options allow you to precisely define when the clock starts and stops on your issues, which is particularly useful when issues move through the same statuses multiple times. By customizing these settings, you can focus on the specific part of the issue’s lifecycle that matters most to your analysis.
Available options:
First transition to status: starts or pauses the timer the first time the issue transitions to a selected status. This option is a default for the “Start timer on” field, meaning the timer starts when an issue first enters an “In Progress” status.
Last transition to status: starts or pauses the timer the last time the issue transitions to a selected status. This option is the default for the ”Pause timer on” field, meaning the timer stops when an issue last enters a “Done” status.
First transition from status: starts or pauses the timer the first time the issue transitions from a selected status.
Last transition from status: starts or pauses the timer the last time the issue transitions from a selected status.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
The Timer is available only for one status. If the “In Progress” or the “Done” status category includes a few statuses and you did not clarify which one status you want to track exactly, all “Timer” options are blocked. |
| Expand | ||
|---|---|---|
| ||
There are a few scenarios to help identify what this setting is about.
|
Calculation method
Calendar: this option calculates the total calendar units (days, weeks, months) an issue remains in the "In Progress" status, including weekends and holidays. For example, if an issue enters "In Progress" on Wednesday and leaves it on the following Thursday, the Cycle Time will be 8 calendar days.
The calculation takes into account time zone settings, holidays and weekends based on your Work schedule.
The default duration of the “one day” for the Calendar option is 24 hours.
Duration: this option only calculates the actual working time when the issue was in "In Progress," excluding weekends, holidays, breaks, and non-working hours which you can setup in the Work schedule. In the same example, from Wednesday to the following Thursday, the Cycle Time would be 6 working days, as Saturday and Sunday are weekends (by default) and are excluded.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Set the Work Schedule during the Calculation method selection ensures that time-based metrics accurately reflect either calendar days or actual working hours, including breaks and holidays. It helps avoid misleading results. |
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The default Work schedule is the next:
By default, the work week has 5 days, and the work day has 8 hours.-
|
