Timing screen helps you to understand how longs it takes to complete a task. Track your lead and cycle times, see how long it takes for a task to go through each individual state in your workflow. Find the bottlenecks in your process to pinpoint areas for improvement.
TRACK LEAD AND CYCLE TIMES
Lead time is the total time that elapses from the creation of a task until its completion.
Reaction time is the time that elapses from the creation of a task until the work is started.
Cycle time is the total time that elapses from the moment when the work is started on a task until its completion.
SEE HOW WORK IN PROGRESS AFFECTS YOUR CYCLE TIMES
Lead time trend shows your average lead time during the last 30 days. You can filter the data according to task type so that you can track a specific aspect of your work such as bugs, user stories, or support tickets.
The yellow trend line shows the average number of tasks in progress (WIP) at any given time.
SEE BREAKDOWN BY THE RESOLUTION TIME
A breakdown of Cycle time shows the distribution (histogram) of the tasks completed during the last 30 days, based on the resolution time.
You can customise the date ranges in the chart settings so that the buckets reflect your typical resolution times.
CLICK-THROUGH TO SEE INDIVIDUAL TASKS BEHIND THE NUMBERS
You can click through to see the individual tasks behind the numbers.
A click-through on a date range shows the tasks having cycle time within that range. See the tasks that took longest or shortest time to complete. Use to plan your future work and to detect anomalies.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks so in both of those cases cycle time would be undefined.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to "open" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default but you can chance that in the chart settings by selecting 'Exclude non-business hours'.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when task is in progress so the time spent on "done" state is not included in the calculation.
What if a task is moved from “not started” state directly to “done” without going through any of the “in progress” states?
In that case the it's cycle time will be zero. It will also be counted as zero for all the in progress states, which will be reflected in the average timings reported in the Time in state chart.
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "open" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “open” workflow state, then the reaction time is zero.
Have questions? Email at firstname.lastname@example.org