Skip to content
This repository has been archived by the owner on Dec 16, 2020. It is now read-only.

Use correct task count in sprint snapshots #219

Merged
merged 1 commit into from Mar 4, 2016
Merged

Conversation

manicki
Copy link
Member

@manicki manicki commented Mar 3, 2016

This would prevent a bug reported in https://phabricator.wikimedia.org/T128594 from appearing in sprints closed after this patch is deployed.

tl;dr: task_count field of the snapshot has always been set to 1.
When not using story points estimates, burn down chart's remaining line and burn up chart's scope line of finished sprints are based on the task count defined in the snapshot (as the sprint has finished, no "live" data is fetched from Phabricator).
Among all changes in #215 setting task_count of the snapshot got broken. Dude who merged that PR was too blind to have noticed this problem.

This fix will of course not affect already existing snapshots. Task counts of those should be adjusted, I am afraid, manually.

I'd like to have this covered by unit test. Problem is that method creating a snapshots relies heavily on the global state (per App:make('phabricator'). This got me thinking if the createSnapshot method really belong to Sprint class.
Thus no test for now but I'd like get back to it rather soon.

WMDE-Fisch pushed a commit that referenced this pull request Mar 4, 2016
Use correct task count in sprint snapshots
@WMDE-Fisch WMDE-Fisch merged commit ea61525 into master Mar 4, 2016
@WMDE-Fisch WMDE-Fisch deleted the snapshot-task-count branch March 4, 2016 09:30
@WMDE-Fisch
Copy link
Contributor

to avoid more broken snapshots I merged this - test will follow

@WMDE-Fisch
Copy link
Contributor

Ah, I see, ignore me, there's a separate PR for the test, right?

the other PR is not related to this issue but to another :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants