Aggregated endpoint for Iteration Burnup / Burndown timeseries
We need to create Burnup(#222750 (closed)) and Burndown(#222741 (closed)) charts for the Iteration report.
Currently, burnup/burndown charts for milestones are created by passing state events to the front end and the front end parses the series and renders the graph. We want to refactor this to compute the time series on the backend (either in Ruby or the DB). Given that we want to deliver these graphs for the Iteration report, I thought it made sense to start by creating this aggregated endpoint for the Iteration report, and then we can backport the refactor into the Milestone graphs.
There's some discussion here for additional context: #213334 (comment 372510648)
There is a closed WIP MR here that may be helpful as reference: !31713 (closed) Backend Tasks:
-
reuse/refactor milestone burnup chart service code for iteration - (!41280 (merged)) -
add Graphql endpoint to fetch iteration burnup/burndown data - (!41666 (merged))
Done when:
-
The frontend can request the necessary timeseries data to render Burnup and Burndown charts on the iteration report page.