| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Metric
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).
You can customize which statuses to count as “Done” - read more here.
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.
Issue state
Define the issue state you want to include in the chart building.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Please note that the “Issue state” just filters the issue’s scope. Some issues may not appear in the Cycle Time Histogram and Cycle Time Trend Charts when applying the “Issue state” filter options other than “Done.” |
You can select the exact issue state scope from the following:
Done: only issues that were “Done” during the selected Time frame.
”Done” issues means also “Updated”. However, they do not have to be “Created” in the same Time frame.Updated (any status change): only issues where any status changes were made from the first date of the selected Time frame.
”Updated” issues mean any status change during the same status category (for example, status change within the “In Progress” status category).
In Jira, "Created" counts as "Updated," so this option will include newly created issues as well.Created: completed (“Done”) issues that were created during the selected Time frame.
Any: includes all issues within the selected Time frame, regardless of their state.
The application is used the following JQL request to get the issue list for the “Any” issue state selected:(created >= start AND created <= end) OR (status WAS IN (...in progress statuses) DURING (start, end)) OR (status CHANGED TO (...done statuses) DURING (start, end))
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".
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" for the Cycle Time Histogram and Cycle Time Trend Charts. 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".
By default, charts take all statuses of from the “Done” status category are predefined.Exception: the Done Statuses option is not available for the Time in Status Cycle Time 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 Time in Status Cycle Time Chart aims 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.
| Expand | ||
|---|---|---|
| ||
Imagine your team includes Developers Team and QA Team with the following statuses of the workflow.  For the Developers Team work starts from the “In Progress”, passes the “In Code Review” status, and can be considered as “Completed” when the issue moves to the “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 as “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.
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
If "First/Last transition to" is used as the "Pause timer on" option, then only issues that are currently/during the selected time frame in “Done” status have the Cycle/Lead Time metric. |
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.-
|
