What is Flow Health?
Flow Health gives you a real-time view of how every in-progress work item is performing relative to your team’s historical delivery patterns. Instead of waiting for a standup to discover that a ticket has been stuck for two weeks, Flow Health flags items that are taking longer than usual — so you can intervene early, unblock your team, and keep work flowing.
How to enable Flow Health
Flow Health is enabled per project. To turn it on:
Within app:
Open Quantify and go to Projects
Find the project you want to enable it for
Toggle the Flow Health switch to on
Within Jira:
Open Space (Project) setttings
Go to apps / Quantify
Toggle the Flow Health switch to on
Once enabled, Flow Health will appear as a tab on your Kanban board and as a panel on individual Jira issue pages for that project.
Understanding health status
Every in-progress work item is assigned a health status based on how its current cycle time compares to similar completed items from the last 90 days. Items are compared against others of the same issue type, so a bug isn’t measured against an epic.
There are four health tiers:
Status | Color | What it means |
Ahead | Blue | Faster than 50% of similar items. Moving quickly. |
On Track | Green | Within the normal range (50th–80th percentile). No action needed. |
At Risk | Yellow | Slower than 80% of similar items. Worth keeping an eye on. |
Delayed | Red | In the slowest 5%. Likely blocked or stalled — needs attention now. |
How are percentiles calculated? Quantify looks at all items of the same issue type that were completed on this board in the last 90 days. It calculates the 50th, 80th, and 95th percentile cycle times from that set, then compares each in-progress item against those thresholds. The more completed items you have, the more accurate the benchmarks become.
The Flow Health dashboard
Navigate to the Flow Health tab on your Kanban board. You’ll see a grid of columns, each showing:
A progress bar with the health distribution — how many items are ahead, on track, at risk, or delayed
Health dots — one colored dot per work item, sorted by severity (red and yellow first)
An item count showing total work items in that column
Grouping options. By default, the dashboard groups items by board stage (your workflow columns). Use the dropdown in the top-right to switch between:
Stage — see health by workflow column (e.g., “In Progress”, “Code Review”)
Issue Type — see health by type (e.g., Bug, Story, Task)
Assignee — see health by team member
Epic — see health by parent epic
Click any column to open the item list below.
The item list
When you click a column, the item list appears showing every work item in that group. By default, it only shows items that need attention (at risk or delayed). You can toggle “Show healthy” to see all items.
Each item shows:
Health dot — color-coded status at a glance
Issue key — clickable link to the Jira issue
Summary — the issue title
Assignee — who’s working on it
Lead time — total days since the item was created
Days in stage — how long it’s been in its current workflow step
Items are sorted by severity: delayed items appear first, then at risk, then on track, then ahead.
Issue side panel
When Flow Health is enabled for a project, a health indicator appears in the Quantify panel on individual Jira issue pages. This lets anyone viewing an issue in Jira see its current health status without leaving the issue.
Notifications (coming soon)
Flow Health can detect when an item’s health status changes — for example, when a ticket moves from “On Track” to “At Risk.” Notification configuration is coming in a future update.
Tips for delivery managers
Use it in standups. Open the Flow Health dashboard at the start of your daily standup. Group by stage and focus on columns with red and yellow dots — these are your discussion topics.
Group by assignee to spot overload. If one team member has multiple at-risk or delayed items, they may be context-switching too much or blocked on something they haven’t raised.
Group by epic to check initiative health. Quickly see whether a specific initiative has concentration of delays that could affect a deadline.
Focus on “Needs Attention.” The item list filters to at-risk and delayed items by default. Start there — if no items need attention in a column, your team is in good shape.
Check lead time vs. days in stage. An item with a high lead time but low days in stage may have been bounced around. An item with high days in stage is likely stuck right now.