-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue #2471] Update SprintBurndown
to use GitHubIssues
dataset
#2618
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM. For clarity, do plan to keep using this once everything is connected with Metabase? Do you plan on using both?
@acouch Great question! @DavidDudas-Intuitial and I were just talking through this yesterday. I think the tentative plan is to run both in parallel for 2-3 sprints (maybe less) just for quality control then we'll likely deprecate Sprinty McBurndown reports once we can support as is / as was reporting in Metabase. |
The base branch was changed.
Switches SprintBurndown to use the GitHubIssues dataset instead of SprintBoard
Updates burndown entry point to only expect one input file.
Updates SprintBurnup to use GitHubIssues instead of SprintBoard
2c7b9d4
to
a55cdd3
Compare
@DavidDudas-Intuitial I rebased this PR on @acouch Welcome your review too if you'd like to take another look. |
SprintBurndown
to use GitHubIssues
dataset
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Nice work removing the redundant code.
Summary
Stacked PR that builds on #2539 to replace the
SprintBoard
dataset inSprintBurndown
andSprintBurnup
with the newGitHubIssues
dataset.Fixes #2471
Note:
Once we merge in #2539 I'll rebase this branch onRebased ✅main
and change the base for the PR tomain
Time to review: 10 mins
Changes proposed
SprintBoard
dataset withGitHubIssues
in theSprintBurndown
andSprintBurnup
metricsSprintBurnup
andSprintBurndown
Context for reviewers
make delivery-data-export POINTS_FIELD="Story Points"
make sprint-burndown
Additional information
You should see a chart that looks like this:
And it should output the following stats: