Agile Cycle Time Charts for Jira Dashboard

A cycle time chart shows how long work items take to travel through a team's workflow – from the moment active work starts to when the item is marked done. Agile teams use Agile Cycle Time Charts to gauge delivery speed, evaluate process consistency, and locate stages where work stalls. The three most common forms are the cycle time histogram (how completion times are distributed), the cycle time trend (whether the team is getting faster or slower), and the time in status report (which statuses consume the most time).

Cycle time starts when work begins (e.g., an issue moves to "In Progress") and ends when it is done. Lead time starts earlier – typically when the issue is created or enters the backlog – and also ends at completion. In the Agile Cycle Time Charts gadget, you can select either metric in the Calculation settings – each with its own timer configuration – so both lead time and cycle time measurements coexist in the same gadget.

A time in status report breaks an issue's total duration into the time spent in every individual workflow status. The Agile Cycle Time Charts gadget offers three modes – absolute (raw hours or days of status time), ratio (each status as a share of total cycle time), and average (mean duration per status across all analyzed issues). This makes it straightforward to see whether delays sit in development, review, QA, or any other stage.

Jira's native control chart plots individual issue durations on a scatter plot with percentile bands. The Agile Cycle Time Charts histogram provides a complementary view – grouping completion times into frequency bands with P50/P85/P95 percentile lines to assess predictability. Combined with the cycle time trend chart, it delivers richer predictability analysis than the built-in Jira control chart.

Agile Cycle Time Charts address the core flow-efficiency questions teams face:

• Are process changes making a difference? – The cycle time trend chart tracks percentile shifts over sprints or calendar periods
• Which workflow stage is the biggest bottleneck? – The time in status chart ranks statuses by the time they consume
• Are we within SLA limits? – target lines on the chart flag the moment cycle time exceeds an agreed threshold
• How predictable is our delivery? – The histogram reveals whether completion times cluster tightly or spread across a wide range

Agile Cycle Time Charts are free forever for teams of up to 10 users. Larger teams pay based on seat count – use the pricing calculator to see the exact cost for your instance. Every new installation starts with a 30-day full-feature trial – no credit card needed.

Go to the Atlassian Marketplace listing, click "Try it free," and follow the installation steps. Once the app is on your Jira instance, open any dashboard, click "Add gadget," search for Agile Cycle Time Charts by Broken Build, and place it where you need it. The gadget is ready to configure immediately.

Yes. Under Calculation settings, you can define a Work Schedule that excludes weekends, public holidays, and custom time-off periods. All cycle time, lead time, and time in status values then reflect actual working hours rather than raw calendar time.

Yes. Every chart supports drill-down to the issue list – click any bar, segment, or data point and the gadget shows the exact issues behind it. Combined with the breakdown feature, you can filter by assignee, issue type, release, or any Jira field before drilling down.

Yes. The Data Source settings accept any number of boards (Scrum or Kanban), projects, releases, epics, initiatives, or JQL queries. All selected sources merge into a single dataset, so one cycle time histogram or lead time report can represent the combined flow of several teams or an entire portfolio.