In one project, I noticed an issue that looked like any other completed task but had taken much longer than expected. Flow Time Report showed that the main delay was outside development: the issue had spent several days in Review before moving back to In Progress.
Looking through the transition history helped me understand what had happened. In this case, the delay came from several rounds of waiting and repeated checks, rather than the complexity of the task itself. That pattern would have been easy to miss by looking only at the creation and completion dates.
For me, this was a useful example of why it helps to examine the time spent in each status alongside overall cycle time. It makes it easier to understand where the process is slowing down and which improvements are worth considering first.
Disclosure: I’m with TypeSwitch, the maker of Flow Time Report on the Atlassian Marketplace.
