Jira KPI Dashboard: Key Metrics, Examples & How to Track Performance

You check your Jira dashboards, but you still can’t answer a simple question:

“Why are we slow?”

Tasks are moving. Sprints are closing. But execution seems unpredictable—deadlines are being missed, work is getting stuck, and no one can clearly explain why.

That’s because standard Jira dashboards show activity, not actual performance.

The Jira KPI dashboard changes that. It helps you see how work is actually flowing through your system, where time is being wasted, and what’s really slowing down your team.

In this guide, you’ll learn:

• Which Agile KPIs are actually important (and which aren’t)
• How to track them in Jira step by step
• How to create a dashboard that gives you real, actionable insights

Ultimately, you’ll be able to turn Jira into a system for improving execution, not just tracking tasks.

What Is a Jira KPI Dashboard?

A Jira KPI dashboard is a centralized view of key performance metrics that helps teams quickly understand delivery speed, bottlenecks, and team performance — without digging through multiple reports.

It aggregates critical KPIs such as cycle time, lead time, WIP, and more to answer key questions:

• Are we delivering on time?
• Where is work getting stuck?
• Is the team performing consistently?

While Jira’s native dashboards show basic data, deeper analysis requires tracking additional metrics, such as how long tasks stay in each workflow stage.

With the Time in Status app (developed by SaaSJet), you can track time in status metrics and get better analysis of Jira KPIs.

Why KPI Metrics Matter in Agile Teams

Without KPIs, Jira shows activity — not performance.

You see tasks moving, but you don’t see:

• where time is actually lost
• why delivery slows down
• whether the team is improving

Instead of guessing, teams rely on data such as cycle time, lead time, throughput, WIP, and more. This helps them:

• identify bottlenecks quickly
• predict delivery timelines more accurately
• focus on the result, not the process
• improve work based on facts

Agile and DevOps also shift the focus from people to the system — what matters is how the work is progressing, not who is doing the work.

Essential Agile KPI Metrics

Most teams know what to track. The real problem is:

Where can I see this metric in Jira, and how can I add it to my dashboard?

Below are 7 essential KPIs, explained in a simple way, along with how to track them in Jira dashboards.

1. Cycle Time & Lead Time

Cycle Time: Measures the time issues spend between In Progress → Done.

Lead Time: Calculates the time issues spend from Created → Done.

Where in Jira: Control Chart (board → Reports).

Dashboard: Cannot be added natively.

To see cycle time and lead time on the Jira KPI dashboard, teams use the Time in Status app — specifically the Accurate Time in Status gadget — to track this on dashboards.

It allows them to track the time issues spend in different statuses and group those statuses based on cycle time and lead time.

2. Throughput

What it is: Number of completed tasks per sprint.

Where in Jira: Jira doesn’t have a built-in “Throughput” metric, but you can easily set it up using a filter and a gadget.

Step 1: Create a filter

Use this JQL:

status = Done AND resolved >= startOfSprint()

This shows all issues completed in the current sprint.

 Step 2: Add a gadget

Add the Filter Results Gadget to your dashboard and select the saved filter.

When this is a problem:

• If throughput drops while WIP stays high → your team is overloaded.
• If throughput is unstable → planning is unreliable.

3. Work in Progress (WIP)

What it is: Number of active tasks.

Where in Jira: Board.

Dashboard setup:

• Filter: status in (“In Progress”, “Review”)
• Gadget: Filter Results

When this is a problem:

• If WIP is high → multitasking reduces delivery speed
• If WIP keeps growing → work is getting stuck

4. Active vs Waiting Time

This concept compares how much time a task is actually being worked on vs how much time it is just waiting in the process.

Simple Example:

A task takes 10 days total:

• 4 days → active work
• 6 days → waiting

👉 Most of the time (60%), the task is not moving.

Where in Jira: Jira does not separate active time and waiting time metrics. 

To see this, teams use plugins like Time in Status, where the Accurate Time in Status gadget shows how long tasks stay in active vs waiting stages.

5. Time in Status

What it is: The time issues spend in each workflow stage.

Where in Jira: This is a core limitation of Jira.

The Accurate Time in Status gadget lets you:

• see time issues spent per status
• detect bottlenecks
• analyze trends

6. Transition Count

What it is: Shows how many times an issue moves between statuses during its lifecycle.

Where in Jira: Jira does not provide the Transition Count metric. However, using the Accurate Time in Status gadget, you can track transition count (how many times issues move between statuses).

This helps you understand not just how long work takes, but also how stable your process is.

Usually, real Jira KPI dashboards are always a combination of native Jira gadgets and additional (time-based) metrics.

How many times tasks move between statuses.

7. Sprint Burndown

What it is: A chart that shows how much work remains over time during a sprint.

Where to track it in Jira: With the Burndown Status Tracker gadget (developed by SaaSJet), you can:

• track how work moves between statuses over time
• see distribution of tasks across workflow stages
• identify exact stage where work accumulates
• detect bottlenecks inside the sprint

Jira KPI Dashboard Examples

Understanding what a KPI dashboard in Jira looks like in practice is just as important as knowing the metrics themselves. Below are real-world examples of how teams can structure their dashboards based on their goals and roles.

Project KPI Dashboard

A Jira project KPI dashboard provides a high-level view of delivery performance across a project. It is typically used by project managers, product owners, and stakeholders.

(approximate visualization)

Purpose:
This dashboard helps you quickly see if delivery is at risk — and exactly where.

Typical questions it answers:

• Are we delivering on time?
• Are there delays in the workflow?
• Where are bottlenecks forming?

Example scenario:
The product development team is preparing for a major release scheduled in two months. Stakeholders need visibility into the progress of the work and the associated risks, without delving into task-level details.

Key Jira KPI metrics to include:

• Cycle Time & Lead Time → via the Accurate Time in Status gadget
• Throughput (tasks completed per sprint) → Filter Results gadget
• Created vs Resolved Chart → to track scope vs delivery balance
• Time in Status → to identify workflow bottlenecks

Insights this dashboard provides:

• If the lead time is increasing, the delivery is slowing down
• If throughput is inconsistent, planning is unreliable
• If issues accumulate in one status, it signals a process bottleneck

This type of jira KPI reporting helps stakeholders make faster, data-driven decisions without relying on subjective updates.

Jira Team KPI Report

This dashboard focuses on team-level performance and workflow stability. It is mainly used by team leads and delivery managers.

(approximate visualization)

Purpose:
To monitor how efficiently the team works and identify process issues early.

Typical questions it answers:

• Is the team overloaded?
• Is work flowing smoothly?
• Are tasks frequently getting stuck or reopened?

Example scenario:
The development team consistently fails to meet its sprint commitments. The team lead should determine whether the problem stems from excessive commitments, bottlenecks, or unstable processes.

Key KPI metrics in Agile teams:

• Work in Progress (WIP) → Filter + Filter Results gadget
• Throughput → completed tasks per sprint
• Reopen Rate → indicates quality issues
• Transition Count → via Jira KPI plugin (process stability)
• Time in Status → to detect delays in specific stages

Insights this dashboard provides:

• High WIP → multitasking and reduced efficiency
• High reopen rate → quality or requirement issues
• High transition count → unstable or chaotic workflow

This is one of the most practical Agile KPI examples, as it directly helps teams improve their day-to-day work.

Agile KPI Dashboard for Scrum Teams

An Agile KPI dashboard for Scrum teams focuses on sprint predictability, delivery consistency, and continuous improvement.

(approximate visualization)

Purpose:
To support sprint planning, retrospectives, and delivery forecasting.

Typical questions it answers:

• Can we reliably deliver what we plan?
• Is our velocity stable?
• Are we improving sprint over sprint?

Example scenario:
A Scrum team wants to improve sprint predictability and reduce the number of tasks that spill over into the next sprint.

Key agile KPI metrics to include:

• Velocity → Sprint Report (native Jira)
• Sprint Burndown → to track progress within a sprint
• Throughput → actual completed work
• Cycle Time → to understand delivery speed
• WIP → to limit overloading

Insights this dashboard provides:

• Stable velocity → predictable delivery
• High spillover → poor planning or blockers
• Long cycle time → inefficiencies in execution

Among all KPI metrics in Agile, this dashboard is the most actionable for continuous improvement during retrospectives.

Time-Based KPI Dashboard (Advanced)

This is the most advanced version of a Jira KPI dashboard, focused on time-based analysis and flow efficiency.

(approximate visualization)

Purpose:
To deeply understand how work moves through the system and where time is lost.

Why it matters:
Most Jira KPI metrics show what is happening. Time-based metrics show why it is happening.

Example scenario:
A team delivers fewer features than expected, even though workload and team size remain the same. The issue is unclear.

Key metrics (requires Jira KPI plugin like Time in Status):

• Time in Status → time spent in each workflow stage
• Active vs Waiting Time → value vs delay
• Cycle Time breakdown → per status group
• Transition Count → process inefficiencies

Insights this dashboard provides:

• Tasks spend most of the time waiting, not being worked on
• Review or QA stages create delays
• Frequent status changes indicate process instability

👉 Example insight:

A task takes 8 days total:

• 2 days → development (active)
• 6 days → waiting for review

This clearly shows that the problem is not development speed, but process delays.

This type of jira KPI reporting is critical for mature teams focused on optimization, not just tracking.

How to Build a Jira KPI Dashboard (Step-by-Step)

Building an effective Jira KPI dashboard is not about adding as many gadgets as possible — it’s about selecting the right metrics that give clear, actionable insights into your workflow.

Follow these steps to create a practical and useful dashboard:

Step 1: Define your goals
Start by understanding what you want to track. Different dashboards serve different purposes:

• Delivery speed → cycle time, lead time, throughput
• Team performance → WIP, reopen rate, transition count
• Process efficiency → time in status, active vs waiting time

Your choice of KPI for agile teams should always reflect real business or delivery goals.

Step 2: Choose the right metrics
Avoid tracking everything. Focus on a small set of high-impact agile KPI metrics, such as:

• Cycle Time & Lead Time
• Throughput
• Work in Progress (WIP)
• Time in Status
• Transition Count

These are the most practical KPI metrics in Agile, used by real teams to improve delivery and predictability.

Step 3: Create filters (JQL)
Most Jira dashboard gadgets rely on filters.

Examples:

• Throughput (completed issues):
  status = Done AND resolved >= startOfSprint()
• Work in Progress:
  status in (“In Progress”, “Review”)

Save these filters — they will power your dashboard.

Step 4: Add dashboard gadgets
Go to Dashboards → Create dashboard → Add a gadget and configure:

• Filter Results Gadget → throughput, WIP
• Created vs Resolved Chart → delivery vs scope
• Sprint Report / Burndown (via board) → sprint tracking

For advanced insights, use Time in Status add-on and its gadgets to add:

• Time in Status
• Cycle Time & Lead Time
• Active vs Waiting Time
• Transition Count

This is where basic Jira KPI reporting becomes real process analysis.

Step 5: Organize for clarity
Structure your dashboard so it’s easy to read:

• Top → key summary metrics (cycle time, throughput)
• Middle → flow metrics (WIP, created vs resolved)
• Bottom → detailed analysis (time in status, bottlenecks)

A good Agile KPI dashboard should answer questions in seconds — not require investigation.

Step 6: Review and improve regularly
Your dashboard is not static. As your team evolves, your Agile KPI examples should evolve too.

Review it during:

• Sprint retrospectives
• Weekly team check-ins
• Delivery reviews

Remove metrics that don’t provide value and refine those that do.

Final tip:
The best Jira KPI dashboard is the one your team actually uses. Keep it simple, focused, and tied to real decisions — that’s what turns metrics into impact.

Best Jira KPI Plugins for Advanced Reporting

Very often, Jira’s built-in features aren’t enough to analyze team performance, especially when it comes to time-based metrics.

One of the most popular solutions is the  Time in Status app, which transforms raw workflow data into actionable insights. 

Time in Status (by SaaSJet)

The Time in Status app allows to track how long each issue spends in every workflow stage — something Jira does not provide natively in a detailed or dashboard-ready format.

What it does:

• Tracks time spent in each status for every issue
• Calculates the average time per status
• Provides multiple report types (including time, status count, and transition count)
• Displays data in both tables and visual charts for easier analysis 

If you want to move beyond basic metrics and build a truly actionable Agile KPI dashboard, the Time in Status plugin is essential. It transforms Jira from a task tracker into a system for analyzing flow, identifying inefficiencies, and continuously improving delivery performance.

Start your free Time in Status trial and turn Jira data into actionable insights.

FAQ