Burn Down Burn Up report option for reports

[devra_a_komenda]

Provide the burn down burn up report algorithm's, offered through Backlogs, in reports that can be embedded on a primary item.  The reporting options will allow us to pass the primary item keys through parameters populated at Query at Runtime.  After which we would be able to embed the report on the primary item.  In our primary application each one of our primary items are projects with many tasks and time assigned to them.  The burn down burn up reporting algorithm would provide an immediate view in the project status.  If we used the Backlogs option as it is offered now for each primary item the process is inefficient to setup one up and access it from a separate location.   We want to access this information for within the primary items.

[Dave Easter]

Burn down rates / progress reports were introduced in SBM Reporting in SBM 11.3.1:

Predictive Reporting: The new Estimated Backlog Trend report provides a comparison of activities completed against activities planned over time. This report can display future trend data based on the current rate of velocity and estimated completion dates, and can also include end-of-sprint milestones. This enables teams to view the projected burn down rate and the progress currently being made along that line.

[devra_a_komenda]

##- The new Estimated Backlog Trend report you reference, from what I can
determine, does not provide a Tab to “Set Estimates”. We are looking for a
comparison of planned hours to actual hours against a project start to SLA
date. The burn down burn up report within the Backlog menu option provides
for field assignments to planned estimates and actual estimates. The burn
down burn up report uses those fields to report units based on those hours
rather than item counts. This is what we are looking for in the embedded
report version.
Are there plans to improve Estimated Backlog Trend report allowing us to
report against estimate fields of our choosing other than item counts? -##