Skip to content

feat(jira): persist Sprint Report snapshot for accurate committed/com…#9010

Open
bramhanandlingala wants to merge 1 commit into
apache:mainfrom
bramhanandlingala:fix/#8967
Open

feat(jira): persist Sprint Report snapshot for accurate committed/com…#9010
bramhanandlingala wants to merge 1 commit into
apache:mainfrom
bramhanandlingala:fix/#8967

Conversation

@bramhanandlingala

Copy link
Copy Markdown
Contributor

Summary

Jira only tracked issues' current state, so committed/completed sprint velocity had to be approximated from resolution dates — which mis-attributes issues that span multiple sprints, causing errors in adjacent sprints.

Changes Made

  • New _tool_jira_sprint_reports table + collector/extractor — persists Jira's own frozen Sprint Report snapshot per closed sprint.
  • Added committed_story_point/completed_story_point to the domain sprints table, populated by a new convertor.
  • New "Sprint Velocity" panel on the Jira Grafana dashboard (mysql + postgresql).
  • Updated linear/zentao e2e snapshot fixtures for the new shared domain columns.

Does this close any open issues?

Closes #8967

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: Persist Jira Sprint Report snapshot to enable accurate sprint velocity (committed & completed)

1 participant