Repository navigation
Conversation
The Sprint Velocity panel joined sprints with board_sprints only by board_id, so it also showed sprints owned by other boards (Jira returns every sprint any of the board's issues has been in) and ignored the dashboard time range. Only keep sprints whose original_board_id is the selected board and whose completed_date is within the selected range. Closes apache#9369
dmorfav
force-pushed
the
fix/jira-sprint-velocity-filter
branch
from
November 11, 2026 13:44
317987d to
3c091f5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the Sprint Velocity: Committed vs Completed Story Points [Closed Sprints] panel of the Jira dashboard (
grafana/dashboards/mysql/Jira.json).The panel joined
sprintswithboard_sprintsonly byboard_id. The Jira Agile API returns, for a board, every sprint any of its issues has ever been in, so the panel also plotted sprints owned by other boards. It also had no$__timeFilter, so every historical sprint was shown regardless of the selected range. On long-lived boards this made the chart unreadable.This PR adds two conditions to the panel query:
Verified on v1.0.3-beta19 against a real Jira board: before, the panel mixed sprints from several unrelated boards going back years; after, it shows only the board's own closed sprints within the selected range. No other panels are touched.
Does this close any open issues?
Closes #9369
Screenshots
Not included, as they contain internal sprint names. Happy to describe the before/after in more detail if needed.