fix: show only current increment's sprints, not old spilled ones#2
Merged
Conversation
Spilled issues carry their entire sprint history in Jira's Sprint field, so the sprints referenced by an increment's issues include old sprints from previous increments. These were surfacing as the current increment's sprints in the dashboard, epic detail, epics table, and sprint-completion views, confusing users. Sprint names encode the increment as `<increment>:<sprint>` (e.g. `Pegasus 25:2`). A new domain module parses that convention to identify which increment each sprint belongs to, infers the increment in view (anchored on sprints overlapping its date window, so past increments with forward-spilled work still resolve correctly), and filters the "increment sprints" displays to just the matching increment. The spillover report still shows the old sprints, since that's its purpose. The convention is the default but configurable in Settings -> Advanced (a regex with two capture groups plus sprints-per-increment), since it varies company to company. Closes #1
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
2 participants
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.
Spilled issues carry their entire sprint history in Jira's Sprint field,
so the sprints referenced by an increment's issues include old sprints
from previous increments. These were surfacing as the current
increment's sprints in the dashboard, epic detail, epics table, and
sprint-completion views, confusing users.
Sprint names encode the increment as
<increment>:<sprint>(e.g.Pegasus 25:2). A new domain module parses that convention to identifywhich increment each sprint belongs to, infers the increment in view
(anchored on sprints overlapping its date window, so past increments
with forward-spilled work still resolve correctly), and filters the
"increment sprints" displays to just the matching increment. The
spillover report still shows the old sprints, since that's its purpose.
The convention is the default but configurable in Settings -> Advanced
(a regex with two capture groups plus sprints-per-increment), since it
varies company to company.
Closes #1