Skip to content

How does Fab calculate cycle time?

Total Cycle Time (TCT) runs from an Issue's creation to its latest move to done. Work Cycle Time (WCT) runs from its first move to in progress to that same move to done. Fab shows the median elapsed time for each measure.

The figures include shipped Issues: those whose latest move to done falls within the selected period and which remain done at the report cutoff. Canceled Issues are excluded.

Both measures include waiting and rework. They do not measure active working hours. If you start an Issue on Monday and move it to done on Wednesday, its work cycle time includes the time between those events even if nobody worked on it overnight.

Reopening an Issue preserves the original creation and work-start times. A later move to done becomes the new endpoint. If the Issue is not done at the report cutoff, it is excluded from the completed cycle-time figures.

An Issue moved to done before it ever entered in progress has a total cycle time but no work cycle time. An incomplete history can also leave work cycle time unknown. These Issues do not contribute a zero duration to the WCT median.

Open the dashboard options menu and select About this data to see how many Issues contribute to each figure. WCT also shows how many never started and how many have unknown histories. Different counts can explain why TCT and WCT move differently.

A median is the middle duration after sorting the measured durations. If there are two middle values, Fab averages them. When no duration can be measured, the result is unavailable.