Metrics catalog

Metric	Scope	Grouping / notes
FTPR	Completed features (bugs excluded)	Jira: completion month, changelog-based. ClickUp: completion month by default (group_by: due_date for due-date month), tag-based
Cycle time	Features only	First cycle_start_statuses → done
Lead time	Features only	Created (or lead_start_statuses) → done. ClickUp: may use start/due dates when both set
Avg time in QA	Features only	qa_in_progress_* statuses. excludes qa_ready_*
Throughput	Non-bug features completed	By completion month
Bugs opened / closed	Bug tickets	By created / resolution month
Bug density	Bugs closed ÷ features shipped	Per month
Bug resolution time	Bug lead days	Created → done, by completion month
Bug backlog	Open bugs at month-end	Jira: open fetch + changelog. ClickUp: open task fetch
Bug reopen rate	Bugs closed then reopened	Uses reopen_statuses + done statuses
Bugs by priority	Bugs closed in range	Native priority, or custom urgency_field when set (one source per workspace)
Bug lead by urgency	Bug lead days	Same source as bugs by priority
Lead time by ticket size	Feature lead days	Bucketed by size custom field + value maps
Flow efficiency	Completed features	100 × work / (work + wait) from flow statuses. ≥75% = good
Bottleneck index	Completed features with status history	Statuses >25% of total time flagged. excludes bottleneck_exclude_*
Status distribution	Completed features	Avg days per status per month
Status time heatmap	Same data	Monthly heatmap on Quality Insights
QVI	Quality Velocity Index	(FTPR × throughput) / (max(avg_cycle, 0.1) × 10) per month
QHS	Weighted 0–100 score	See metrics.qhs. month-over-month when prev month in range
Team statistics	Cross-squad table	Range aggregates + current-month FTPR

Date rules: Completion metrics include tickets resolved during the selected range. Tickets created before the range but closed during it are included.

Cards vs charts: Quality Insights summary cards use the full selected range average. Team Statistics current-month columns use the month of the “To” date.