FlowLens
Flow metrics from your real item history, no estimates required.
FlowLens turns synced Jira, GitHub, GitLab, Bitbucket, Linear and Azure DevOps items into flow metrics you can act on. Everything is computed from the items' actual state history, so there is no manual time tracking and no estimation ceremony. Connect a tracker, point a project at it, and the board fills in.
Flow overview
Work is laid out by workflow stage (To Do, In Progress, In Review, Blocked, Done and Cancelled), each with its item count, a proportional bar and the average age of the work sitting there. Click any stage to filter every chart and table below it to just those items; that dwell time is how bottlenecks become visible.
The numbers that matter
Four headline tiles summarize delivery: velocity this week (with the change versus last week), work in progress, cycle-time P50 (the median days from start to done), and blocked rate. Cycle time is also broken into P50, P75 and P95 percentiles, so you see both the typical case and the long tail that actually breaks commitments.
Throughput and velocity
The throughput chart shows items completed per week for the last eight weeks, so you can tell at a glance whether delivery pace is stable, rising or falling, and compare it against what the team is committing to. A rising cycle time next to flat throughput is the classic early sign of trouble.
Aging work in progress
The aging view floats the oldest in-progress work to the top and flags items that have sat far longer than your typical cycle time. Age is colour-coded (green under three days, amber up to a week, red beyond), and stalled items and SLA breaches are highlighted. These are your most likely hidden blockers and the best candidates for a standup question.
Blocked items and bottlenecks
Items flagged or labelled as blocked in your tracker are collected into one list with their blocker reason, so unblocking work can be prioritized explicitly. The bottleneck view adds the average dwell time per stage and marks the worst offender, so you know where work is really piling up rather than where it merely feels busy.
Policies: SLA and WIP limits
Open Policies from the FlowLens header (a project must be selected) to set two kinds of guardrail. An SLA policy caps how many days an item may stay open before it counts as a breach. Give it a label like 'Bugs', an optional item type, and a maximum age in days. A WIP limit caps how many items may sit in one stage at once. Pick a stage (To Do, In Progress, In Review or Blocked) and a maximum count. When either is crossed, a red banner appears at the top of FlowLens and breaching rows are tinted in the aging table. Policies are set per project, and you can add as many as you need.
Filters and the item table
Filter everything by assignee, priority, label or stage; an active-filter count shows how narrowed the view is, and one click clears it. The item table lists title, source, assignee, stage, age and priority, and every row links back to the original item in your tracker.
Syncing
Data refreshes automatically: scheduled background syncs run regularly and, where configured, webhooks push changes as they happen. FlowLens also re-syncs on open when the data has gone stale. The Sync now button forces an immediate refresh, and the header shows when each connected source last synced.
The Toolbox: sources and AI suggestions
The right-hand Toolbox panel gathers the supporting detail: totals and cycle-time percentiles, the project's tracker sources, each connected integration with its sync freshness (fresh, stale or failed), and a Show AI suggestions button that reads your current numbers and proposes concrete next moves. It is also where FlowLens's alert rules are configured without leaving the module.
Insights and alerts
Small live insight cards call out sharp movements (cycle time up sharply versus the last four weeks, velocity dropping this week, or items stalled with no recent activity), red before amber, so the biggest change is first. For anything you want to be told about even when you are not looking, turn it into an alert rule (see Alerts & notifications): FlowLens can watch SLA breaches, WIP limits, stale work and blocked-item counts and message you on Slack or by email.
Saved views
When you have a combination of filters you use often, open Views in the filter bar and choose Save current filters as a view. Give it a name, and tick Share with the workspace if the whole team should have it. From then on, Views applies it in one click. You can delete your own views; shared views from others show a small team icon.
Investment balance
The Investment balance section shows where finished work went over the last six months, split into roadmap, bugs, tech debt and unplanned work, month by month, plus the mix of what is still open. Every ticket is sorted once, by its tracker type, labels and title where they are clear, and by AI overnight for the rest; new tickets are sorted the night after they appear. If an admin sets a monthly cost per person, each category also shows roughly what it cost: the people who finished work that month times that cost, split by each category's share of tickets. It is an estimate based on ticket counts, not hours.
Exporting to CSV
Aging work in progress, the team breakdown and the investment balance each have an Export CSV button. The export contains all rows, not just the page you are looking at.