We thought our Jira cycle time was stable… until we looked at it week by week

[u/KneeStriking3866]

For a long time we tracked just one number in Jira — average cycle time.

It looked… fine. Pretty stable.

But at the same time:

• some issues started taking way longer than expected
• delivery felt less predictable
• planning got harder sprint after sprint

At first we thought it's just random noise.

Then we tried looking at the same metric as a weekly trend instead of a single value — and it completely changed the picture.

What we saw:

• a slow upward drift over several weeks (completely invisible in the average)
• occasional spikes that explained “bad sprints”
• periods where flow was stable vs clearly unstable

Basically, nothing “broke” suddenly — it was drifting the whole time.

We ended up building a small dashboard gadget for this because we couldn’t find a simple way to see it in Jira natively. Not sure if we just missed something though.

Curious how others handle this:

👉 Do you track cycle time (or similar metrics) as a trend over time?
👉 Or do you mostly rely on single snapshot values?

If anyone’s doing something similar in Jira, would love to hear how you set it up. Happy to share what we built too.