# Epic AGILE-64 - Provide sprint reports for active and completed sprints Project: Stream agile Status: in development URL: https://community.openproject.org/work_packages/AGILE-64 ## Detailed specification ### Motivation and background information * material for reflection (retrospective) * indicators for team health-check * helps to understand performance, issues and through that helps the team to improve ### Acceptance criteria How can users access the sprint reports? - via all sprints index page - via ... menu within backlog and sprints page - from the sprint board Information visible on the 1st iteration (static page) - sprint goal - overview over wp \# within the sprint  - number of work packages initially planned for the sprint - number of work packages completed - number of work packages unfinished - number of work packages added additionally to the sprint during the sprint - \[open question\] sprint progress chart (unfinished / completed) - velocity chart (story points based) / more details within \#AGILE-66 - 7 last completed sprints - committed / completed - average calculated based on the completed and visible sprints only (not only the line, but also the number) - burndown chart - we use the existing burndown chart - work package table: Completed work packages - Columns: ID, subject, type, status, assignee - work package table: Unfinished work packages - work package table: Scope change after sprint start Information visible on the dynamic page - graph "Work package status" - showing the status of work packages within the sprint - we use the existing bar chart wp widget - \[open question\]: I think a pie / doughnut chart might work better in order to show how the entire sprint scope splits into statuses. Should we go for bar chart or another one? Julia: bar chart\! - the graph could quickly give an overview over the progress within the sprint - update on the existing graph: when I click on a certain bar I should be forwarded to the work package table (open in new tab) showing all the wp behind the bar, so that the bars are interactive ### Out of scope * changes to the existing burndown chart * burnup chart * Report on estimates * compare estimated workload and workload logged on the wp * "over consumption" (when workload on a WP is > than the initial estimate) * possibility to change the order and size of widgets within the sprint report page * possibility to add new widgets to the sprint report page * possibility to integrate newly provided widgets (e.g. velocity chart) in the project dashboard * further, manual configuration of the velocity chart (e.g. timeline, number of sprints, points vs. wp vs. hours) * usage of baseline functionality All the topics are desired, but will be addressed separately. | Attribute | Value | | --- | --- | | Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=0-1&t=CxY3o2NyF0XJ9kr0-1 | ## Planning | Attribute | Value | | --- | --- | | Roadmap | 2026 Q4 | | Date | 2026-10-23 | | Votes | | | List | Agile Reporting | | Target versions | 18.0.0 | | Sprint | | | Backlog bucket | | | Relevance | Important — Required Short-Term | ## Subitems | ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | AGILE-296 | Feature | Sprint report page with burndown chart widget | tested | | 18.0.0 | Stream agile | Medium | | | AGILE-297 | Feature | Sprint goal on sprint report page | tested | | 18.0.0 | Stream agile | Medium | | | AGILE-303 | Feature | Work package overview on sprint report page | tested | | 18.0.0 | Stream agile | Medium | | | AGILE-304 | Feature | Work package tables (completed, unfinished, added, removed) on sprint report page | in test | Ivana Šugić | 18.0.0 | Stream agile | Medium | | | AGILE-308 | Feature | Rework burndown chart | in test | Ivana Šugić | 18.0.0 | Stream agile | Medium | | | AGILE-360 | Feature | Work packages graph on sprint report page | tested | | 18.0.0 | Stream agile | Medium | | | AGILE-398 | Feature | Enterprise banner on reports page | review approved | | 18.0.0 | Stream agile | Medium | | | AGILE-455 | Feature | Scope change on work package overview widget counting story point changes | tested | | 18.0.0 | Stream agile | Medium | | | AGILE-469 | Feature | Screenreader compatible description of charts | specified | OP Dev Polaris Team | 18.0.0 | Stream agile | Medium | | | AGILE-498 | Implementation | Remove feature flag for reporting | specified | | 18.0.0 | Stream agile | Medium | | | AGILE-467 | Open Point | Apply the backlogs definition of done for the whole reporting page | decided | | | Stream agile | Medium | | ## Bugs and other work packages | ID | Type | Subject | Status | Assignee | Target versions | Module | | --- | --- | --- | --- | --- | --- | --- | | AGILE-274 | Task | Discovery work for sprint reports | closed | Julia Racsko | | | | AGILE-467 | Open Point | Apply the backlogs definition of done for the whole reporting page | decided | | | | ## Details | Attribute | Value | | --- | --- | | Module | | | Enterprise plan | Community (COM) | | Labels | | ## People | Attribute | Value | | --- | --- | | Assignee | Julia Racsko | | Accountable | Rosanna Sibora | | Product manager | Rosanna Sibora | | Designer | Julia Racsko | | Developers | OP Dev Polaris Team | | Requested by | | | Interest by | Black (37919), Home (224196000003952096) | ## Estimates and progress | Attribute | Value | | --- | --- | | Work | 45d 0h · Σ 45d 0h | ## Description As a user I would like to understand the performance of the team within the completed sprint, so that we can reflect on it and get better.