Backend Issue 14: Add Issue Tracking Metrics #15

Closed
opened 2026-05-19 02:28:01 -05:00 by null · 0 comments
Owner

Goal

Expose aggregate tracking data for Forgejo issues in Pipeline metrics.

Suggested Metrics

  • Open issues
  • Closed issues
  • Issues closed in selected range
  • Stale open issues
  • Last successful sync timestamp
  • Repository sync error count

Acceptance Criteria

  • Metrics can be filtered by board and repository where applicable.
  • Empty scope returns zeroes.
  • Pull requests are excluded from issue metrics in MVP.
  • Tests cover mixed open/closed data and stale issue calculation.
  • Existing dashboard metrics tests continue to pass.

Out Of Scope

  • Frontend dashboard widgets, Webhook ingest.
## Goal Expose aggregate tracking data for Forgejo issues in Pipeline metrics. ## Suggested Metrics - Open issues - Closed issues - Issues closed in selected range - Stale open issues - Last successful sync timestamp - Repository sync error count ## Acceptance Criteria - Metrics can be filtered by board and repository where applicable. - Empty scope returns zeroes. - Pull requests are excluded from issue metrics in MVP. - Tests cover mixed open/closed data and stale issue calculation. - Existing dashboard metrics tests continue to pass. ## Out Of Scope - Frontend dashboard widgets, Webhook ingest.
null added the
backend
forgejo
optional
webhooks
labels 2026-05-19 03:32:01 -05:00
null closed this issue 2026-05-20 03:54:42 -05:00
Sign in to join this conversation.
No description provided.