Control Chart or Time in Status? How to Pick the Right Jira Report

[#1]

Jira's Control Chart is a built-in report that tracks Cycle Time and Lead Time for a sprint or product. It answers one question well: how long. Time in Status answers the same question, but with a big difference. The Control Chart gives you a single number per issue, and that number hides what you usually need to know: which status the work is actually stuck in. That single number is still worth having. On a board, under the Reports tab, the chart plots Cycle Time or Lead Time over a period with a rolling average and a standard-deviation band, so you can read how predictable your delivery is handy for a trend read or a retrospective. The gaps show up the moment a total looks wrong and you ask why. Here are three questions the Control Chart leaves open, and how a Time in Status report answers each.
  

Which Status Is the Work Stuck In?

The Control Chart adds up the time across the statuses you pick and gives back a single total. If issues pile up in Backlog the total climbs, but the chart won't point at Backlog. A Status Duration report from Timepiece breaks the same history into one column per status, per issue. Sort by any status column and the slowest issues rise to the top.

 

You still get the roll-ups: with Duration Between Statuses report, you can combine several statuses into one figure you can name yourself: Cycle Time, Lead Time, Resolution Time, whatever your team reports on. The Duration Between Statuses report measures elapsed time from one status to another, which fits SLA-style targets.

  

Are You Counting Hours Nobody Was Working?

The Control Chart can drop weekends and holidays through the board's Working Days setting. But that setting only works a whole day at a time. It has no idea of working hours, so an issue sitting in a status overnight or over lunch keeps counting. Timepiece measures to the hour. A calendar defines the days and the hours within each day that count, plus holidays, lunch breaks, and a time zone, and you can run more than one calendar for teams in different regions. Anything outside those hours simply drops out, so the numbers match the hours people actually work.

What About Work Beyond One Board, or Rework? 

The Control Chart lives on a single board and runs in company-managed projects only. If your work spans several projects, or sits in a team-managed one, it can't reach it. Timepiece reports on any set of issues you can describe in JQL, straight from existing Jira history. It also answers something the chart can't touch: how often an issue bounced back into a status. Status Count and Transition Count surface rework, which is about fixing the process rather than pushing people.

What you want to know	Control Chart	Time in Status report
Total cycle time or lead time	Yes	Yes
The exact status work is stuck in	No	Yes
Time counted by working hours	No	Yes
Scope	One board only	Any JQL scope
Rework	No	Yes

Conclusion: Use Time in Status and Control Chart Together

You don't have to choose. Plenty of teams keep the Control Chart for a fast trend read, then open a Status Duration report the moment a total looks wrong and they need the reason behind it. One tells you something changed; the other tells you where. Time in Status data doesn't have to stay in a table, either. Timepiece can render the same report as a chart: bar, pie, column, or line. So a trend or an outlier status is visible at a glance, on the reporting page or on a dashboard gadget.

To learn more about Timepiece - Time in Status for Jira, it is available on the Atlassian Marketplace.