🤔 Context: A team lead wants to track the cycle time of issues to identify bottlenecks and improve team efficiency.
🌧️ User Problem: Tracking the cycle time of issues from start to completion is crucial for improving team performance, but I don’t have an easy way to monitor this in real-time.
☔ Solution: Time to SLA allows you to track cycle time directly in your workflows, making it easy to monitor progress and optimize team performance.
You can track cycle time through the SLA history feature, which is a helpful tool that displays a record of all the states of your SLA, organized into cycles. Here you can select which SLA’s history you want to view, as well as export it.
Each cycle is made up of a Start and End condition, and by examining your SLA history, you can easily see how long people spent between those conditions, along with all the different statuses of the SLA, like met or exceeded. Whenever an SLA is stopped, the existing cycle will be completed as met or exceeded. And when the issue is reopened, a new cycle starts.
