how to implement flow metrics implementation and reporting in atlassian
Hi,
For small/single team, use Control Chart and Cumulative Flow Diagram. For more reports see
https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/
For broader reporting, Atlassian Analytics has a Flow metrics dashboard template covering throughput, work profile, lead time, cycle time, WIP, and flow efficiency. It requires a Jira data connection in Atlassian Analytics. Atlassian currently lists Analytics and its templates as available to Cloud Enterprise customers. Check your plan and data-source setup before designing around it. See https://support.atlassian.com/analytics/docs/flow-metrics-work-items-view-dashboard-template/
https://support.atlassian.com/analytics/docs/dashboard-templates-for-jira-software/
You can use Confluence for the reporting narrative. You can also place a Jira dashboard or gadget on a Confluence page as a Smart Link.
I would recommend to start in stages by defining the
Hi @Takiar, Vishal (B2B - Infosys),
Jira offers some basic built-in reports, such as the Control Chart and Cumulative Flow Diagram, which you could use. However, these reports are generally limited to individual projects and offer limited flexibility.
A better approach would be to create a dashboard in Jira or, alternatively, a page in Confluence that brings together all the metrics you want to track and keeps them updated in real time.
To achieve this, you will most likely need an app from the Atlassian Marketplace that provides the necessary gadgets and macros for tracking and visualizing these metrics.
For example, our Great Gadgets app (perhaps you already have it installed?!) offers a wide range of Jira dashboard gadgets and Confluence macros for tracking flow metrics.
Here are some examples of flow metrics and the gadgets you can use to track them:
The app can measure many other metrics. Do you have a specific list of metrics to track?
Hope this helps.
Danut
Hi @Takiar, Vishal (B2B - Infosys)
Native Control Chart and CFD cover the basics, but if you want flow metrics (throughput, lead time, cycle time, WIP, etc.) side by side on one dashboard without building JQL filters for each, a Marketplace app is indeed the practical route.
If you are open to that, I recommend Mindpro Insights. I work at Mindpro, and I believe the app can help with your requirements. Insights is a dashboard app with ready-made flow-metric widgets (cycle time, lead time, throughput, etcg) that you can filter by project, team, or sprint and share as a single dashboard, with no scripting or admin setup.
It allows any user to easily create dashboards with 50+ gadgets you can choose from. The gadgets are interactive, which means that when you click on any chart segment, the entire dashboard adapts to your filter.
It has a free trial on the Marketplace if you'd like to compare it with other options:
Happy to answer questions on configuring the metrics
Regards,
Eduardo
Hi Vishal, if you want to start with what's already in Jira before deciding on Analytics or an app, you can cover the core flow metrics with a board plus one dashboard.
Throughput: save a filter such as project = ABC AND statusCategory = Done AND resolved >= -14d and add it to a dashboard with the Filter Results or Two Dimensional Filter Statistics gadget (for example Issue Type vs Assignee). This relies on your workflow setting a Resolution when work is done, so check that first.
WIP: save project = ABC AND statusCategory = "In Progress" and show it in a Pie Chart gadget grouped by Status. It quickly shows where work piles up.
Cycle time: on the board's Control Chart, open Refine and select only the columns you count as active work, leaving out the To Do and Done columns. Quick filters let you split it by issue type.
Before building anything, agree as a team on when work "starts" and when it is "done". Those two definitions matter more than the tool, and they carry over unchanged if you later move to Analytics.
Jira gives you standard reports for flow metrics: the Control Chart (cycle time per work item, with average and rolling average) and the Cumulative Flow Diagram (WIP and growing queues by status).
But both reports have limits and aren't very flexible:
For more advanced reporting, I'd recommend looking at apps on the Atlassian Marketplace. One example is Time in Status, which I work on at SaaSJet. Here's how it helps.
1. Define your metrics once with Status Groups
Combine the statuses that make up each metric into a named group: Lead Time, Cycle Time, or a separate group for waiting statuses to see where work waits.
Add a Work Schedule so non-working hours, weekends, and holidays don't inflate the numbers.
2. Keep flow metrics visible on Jira dashboards
Monitor Time in Status reports and the Burndown Status Tracker gadget directly on your Jira dashboards.
Any report, including your Lead Time and Cycle Time groups, can be shown as a table or chart, so you can track average cycle time, rework loops, and how time in status changes week by week, all with working time only.
The Burndown Status Tracker shows how work moves between statuses and where it gets stuck. From any value on the chart, you can drill into the exact work items behind it.
Together, the two gadgets give your team a shared view for stand-ups, reviews, and stakeholder updates, without anyone asking "where is this ticket?"
Implementing Flow Metrics like Flow Time / Cycle Time, Lead Time, Flow Load, and Flow Efficiency) natively in Jira can be challenging because native Jira operates on a continuous 24/7 clock and doesn't easily calculate elapsed durations between workflow states or store them on individual work items.
To successfully implement and report on flow metrics in Jira, you need two things: accurate flow data calculation (excluding non-working hours) and in-context visibility so your team can act on flow bottlenecks in real time.
If you are open to using a Marketplace app, Timepiece - Time in Status for Jira provides a complete end-to-end framework for flow metrics:
Calculate Core Flow Metrics
Flow Time / Cycle Time & Lead Time: Use the Status Duration or Duration Between Statuses reports to bundle your active workflow statuses (e.g., In Progress + In Review + QA) into a single Cycle Time metric. Custom Business Calendars: Apply custom working schedules to automatically filter out weekends, nights, and company holidays so your Flow Time reflects actual working hours rather than continuous calendar time. Flow Load & Bottlenecks: Identify where work is accumulating using Status Duration and Assignee Duration reports, or set up automated Alarms to ping Slack/Teams when an issue stalls in a status longer than your WIP limits allow.
Make Flow Metrics Visible Right on the Issue View
Rather than keeping these metrics isolated on executive dashboards, you can display live flow data directly where work happens. For a detailed, step-by-step walkthrough on how to set this up, take a look at this Atlassian Community article: How to see time in status data without leaving your Jira issue
You can check out Timepiece - Time in Status for Jira on the Atlassian Marketplace.
Full disclosure: I am on the team that develops Timepiece. Hope this helps.
Hi @Takiar, Vishal (B2B - Infosys) Natively, unfortunately, it's rather not possible to track. The closest native gadget would probably be Cumulative Flow Diagram.
You can try as an option the app I developed - https://marketplace.atlassian.com/apps/1235078?tab=overview&hosting=cloud&utm_source=atlassian&utm_medium=social&utm_campaign=community&utm_content=3289990_Comment_3289990 .
With it you will be able to view:
For PR Cycle time you can try
https://marketplace.atlassian.com/apps/3166628045?tab=overview&hosting=cloud&utm_source=atlassian&utm_medium=social&utm_campaign=community&utm_content=3289990 . Additionally you will get:
Best regards, Alexey
Hi, I'm Alexey 'Ce' from CelesteCS. Since the question is tagged Confluence too: if the flow metrics should end up on a Confluence page next to the team's other reporting, our apps can calculate them there, live from Jira on every page view.
With Math for Confluence (Cloud and Data Center) each metric is one JQL count in a table cell:
JIRAISSUECOUNT("project = ABC AND statusCategory = 'In Progress'")
JIRAISSUECOUNT("project = ABC AND resolved >= startOfWeek()")
JIRAISSUECOUNT("project = ABC AND resolved >= startOfWeek(-1) AND resolved < startOfWeek()")
JIRAISSUECOUNT("project = ABC AND created >= startOfWeek()")
With Reporting for Confluence, a table of the issues resolved in the last 30 days gets a lead time column, DAYS(DATEVALUE(CurrentItem.fields.resolutiondate); DATEVALUE(CurrentItem.fields.created)), and the average in the footer:
DAYS(DATEVALUE(CurrentItem.fields.resolutiondate); DATEVALUE(CurrentItem.fields.created))
One row per past week plus our Chart macro turns throughput into a trend line. One honest limit: cycle time from "In Progress" to Done and time in each status need the issue history, which JQL fields don't provide, so for those the Control Chart or a time-in-status app is still the right tool.
Step-by-step: Flow metrics from Jira on a Confluence page: WIP, throughput and lead time
It looks like you're new here. Sign in or register to get started.
