Tasks Under Epics
Architect & Collaboration Metrics
Counts the number of tasks created under epics during the selected period.
💡 Like outlining before you write, creating tasks under epics shows systematic planning and the ability to break big goals into executable steps.
What It Measures
Counts the number of tasks created under epics during the selected period.
Why It Matters
Measuring ability to break down complex work
Tracking architectural planning discipline (higher values indicate strong planning)
How It's Calculated
Counts each task created with an epic association in the date range.
COUNT(tasks WHERE epic_id IS NOT NULL AND created_at BETWEEN measure_from AND measure_to)Concrete Example
If 18 of your 25 created tasks this month belong to epics, that's 72% epic coverage, strong structured decomposition of larger initiatives.
What Does a Healthy Score Look Like?
Higher is better, tasks under epics indicate structured, intentional planning.
Healthy
Over 60% of tasks linked to epics
Watch Out
30–60% of tasks under epics
Needs Attention
Under 30%, most work is ad-hoc and not linked to strategic goals
What Moves This Metric?
Goes up when…
Strong product planning culture with features driven by epics
Engineering manager actively decomposing roadmap items into tasks
Cross-team initiatives tracked through epic hierarchies
Goes down when…
Reactive work or bug fixes that don't belong to a roadmap epic
Team working without an epic/initiative framework
Epics being created late, after tasks are already underway
Start Tracking Tasks Under Epics
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com