-
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 740] current sprint report #760
[Issue 740] current sprint report #760
Conversation
Setting the BaseMetric.chart attribute during the __init__() method was slow By deferring the execution of plot_results() until BaseMetric.chart is called we can speed up the __init__() method
This property returns the name of the current sprint, which depends on another new method: get_sprint_name_from_date()
Allows users to pass "@current" as the sprint to calculate burndown for the current sprint
This reduces duplication across tests for creating sample SprintBoard data
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!
# fmt: on | ||
matching_sprints = self.sprints.loc[date_filter, self.sprint_col] | ||
# if there aren't any sprints return None | ||
if len(matching_sprints) == 0: |
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.
if len > 1
, should we raise an error rather than silently choosing the first one?
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.
Oh good point! I'll add a quick fix for this before merging
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.
Actually I'm working through a fairly complicated merge conflict upstream, to simplify things I might spike getting this into #685 so I'm just resolving one merge conflict.
892946f
into
issue-314-30k-deliverable-reporting
Enables users to calculate sprint burndown for the current sprint by passing `@current` to the `sprint` argument
Summary
Adds support for calculating sprint burndown using
@current
instead of specifying the name of a sprint. This allows us to set a schedule-based GitHub action that will calculate sprint burndown dynamically.Fixes #740
Time to review: 5 mins
Changes proposed
SprintBoard
SprintBoard.get_sprint_name_from_date()
Which accepts a date and returns the name of the sprint that contains it.SprintBoard.current_sprint
Which returns the name of the currently active sprintSprintBurndown._get_and_validate_sprint_name()
which is used to ensure that the value passed to thesprint
argument is a valid sprint nameBaseMetric.chart
to be a property instead of an attribute whose value was set during__init__()
This change defers the invocation ofplot_results()
which is a slow method and, as a result, it speeds up initialization overall.@current
Context for reviewers
git fetch origin && git checkout issue-740-current-sprint-report
analytics/README.md
file@current
functionality with the following commands:Additional information