Overview
Cycle time measures the total duration it takes to resolve or complete an issue, from its creation to its closurean “In Progress” state to “Done”. Understanding cycle time helps teams identify bottlenecks, optimize workflows, and enhance overall efficiency in the issue resolution process. By analyzing cycle time, teams can pinpoint areas where additional support or process improvements are needed, leading to faster issue resolution and improved project timelines.
...
Cycle time refers to the total time spent on an issue from the moment it is created (or reported) being worked on until it is resolved and closed. It encompasses every step involved in resolving the issue, including:
...
Cycle time is calculated by subtracting the issue's creation “In Progress” timestamp from the timestamp when it is closed or resolved. This provides the total time taken for the entire issue resolution process.
Formula:
Cycle Time = Resolution Time - Creation First “In Progress” Time
For example, if an issue is created on January 1st, started work on it on Jan 2nd, and resolved on January 5th, the cycle time is 4 3 days.
This data is collected from your issue tracking or project management tool (e.g., Jira, GitHub) and provides a clear picture of how long it typically takes to address issues.
...
Advanced Filters: Filter your data using fields and properties located in your project management tool (e.g. JIRA, ADO). Make sure to remove ‘Inactive’ or ‘Removed’ issue states.
...
TIP: Make sure to apply the changes you made to General Filters by clicking ‘Update’.
...