FEATURE
Which epics and people actually absorbed time this period — measured in elapsed hours, not a performance ranking.
Two views: the org-wide dashboard shows a card each for the most active epics and the most active people this period, and each team's page has a dedicated "Reports" tab with the full ranked list plus a weekly stacked chart of the top 5 (grouped as "Others" beyond that). "Active" means time actually elapsed working on items tied to that epic or person — not a score, not an impact rating.
Illustrative data, for demonstration purposes only.
Sourced from the same Jira/Linear work item history already used for Flow Metrics — no separate integration, no manual tracking.
For each completed item, time is measured from when work actually started to when it finished, then rolled up per epic and per person for the period.
Epics and people are ordered by time absorbed — deliberately not framed as a "top performers" leaderboard, because elapsed time isn't the same thing as impact or effort.
The dashboard shows the current snapshot; each team's Reports tab adds the full list and a week-by-week stacked view of where that time actually went.
This measures elapsed time on work, not output, quality, or impact — the same reasoning behind why Capacity & Workload's contributor breakdown exists to spot overload, not to rank people. Use it to find where time is going, not who's "winning."
The epic breakdown in Flow Metrics shows the hierarchy and duration inside one epic. This is the other direction — which epics, across the whole team, absorbed the most time this period.
Capacity & Workload already covers pull requests, deploys and incidents per contributor — this report deliberately sticks to work-item time only, instead of mixing units that don't compare cleanly.
The Reports tab's weekly chart shows whether time is concentrating on the same epics and people week over week, or shifting around — a pattern a single snapshot can't show.
No — it ranks by elapsed time on work items, which isn't the same as effort, quality, or impact. Treat "most active" as "absorbed the most hours," not as a performance judgment.
The Flow Metrics epic breakdown (and its Gantt view) shows the internal timeline of one epic — when it started, when it finished, what's inside it. This report answers a different question: across every epic, which ones absorbed the most time this period.
No — that's what Capacity & Workload's per-contributor breakdown already covers. This report sticks to work-item time specifically, so the two numbers don't get mixed together.