# Feature AGILE-303 - Work package overview on sprint report page
Project: Stream agile
Status: tested
URL: https://community.openproject.org/work_packages/AGILE-303
## Planning
| Attribute | Value |
| --- | --- |
| Date | |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 11 |
| Backlog bucket | |
| Votes | |
| List | Agile Reporting |
| Roadmap | |
| Relevance | |
## OPEN POINTS / FEEDBACK
_No work packages_
## Features and Chunks
_No work packages_
## Bugs and other work packages
| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-459 | Bug | Sprint report: reference dates are missing on View all link | confirmed | | 18.0.0 | | Modules and project features / Backlogs |
| AGILE-454 | Bug | Sprint report automatically opens when we move a wp to a sprint if sprint report was previously opened | confirmed | | 18.0.0 | | Modules and project features / Backlogs |
## Technical Details
| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Backlogs |
| Feature Flag | |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |
## Details
| Attribute | Value |
| --- | --- |
| Pull preview | |
| Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=1-73994&t=vj4zYlvGRDOURFuL-1 |
| Accessibility | No |
## People
| Attribute | Value |
| --- | --- |
| Assignee | |
| Accountable | |
| Product manager | |
| Developers | Tobias Dillmann |
| Designer | Julia Racsko |
| Ordered by | |
| Signed off by | |
| Interest by | |
## Estimates and progress
| Attribute | Value |
| --- | --- |
| PD (min) | |
| PD (max) | |
| Work | |
| Labor costs | |
## Description
Follows ###AGILE-296
**As** an agile user
**I want to** have an overview over the work packages that are part of the sprint
**so that** I can quickly take in the key figures
**Acceptance criteria**
- The sprint report page has a widget showing figures about the work packages of the sprint
- The widget is titled "Work packages within the sprint"
- If possible, the number of work packages currently associated to the sprint are displayed as a pill after the title
- The widget has a progress bar depicting the number of total work packages, the number of finished work packages and the percentage that results in.
- The widget deliberately does not span the whole width on wide screens. The exact width will need to be identified during implementation.
- The widgets shows an additional row of information blocks below the progress bar:
- Each block has a heading, a number representing the total number of work packages and a number representing the sum of story points for those work packages.
- Next to each heading is a "View all" link points to a baseline table view: the reference date (see the blocks) is the sprint start or finish date.
- When baseline is not active on the instance, this link is not shown
- The information blocks for work packages are:
- "Initially planned" - those are the work packages assigned to the sprint on sprint start. The sprint start is the sprint start date.
- Reference date: sprint start or current date (the earlier of the two)
- "Scope change" - the total of work packages added or removed from the sprint.
- Both added and removed should be tallied separately. This is also true for the story points.
- Reference date: Interval between sprint start and the sprint finish date (or the current date if that is earlier).
- "Completed" - those are work packages considered finished
- Reference date: sprint finish or current date (the earlier of the two)
- The number representing the total number of work packages is green.
- "Unfinished"- those are work packages not considered finished.
- Reference date: sprint finish or current date (the earlier of the two)
- The number representing the total number of work packages is grey.
- The information blocks are displayed in a single line (4x1) if space permits. If there is less width, that changes to a 2x2 layout and eventually to a 1x4 layout.
- The exact breakpoints will need to be identified during implementation
- A blankslate is displayed covering the whole widget if the sprint's start/finish dates are not set.
Notes:
- "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)
- Some layout decisions will need to be taken during implementation. Contact @Julia Racsko for confirmation.
- While the sprint start and finish dates are dates (whithout time zones) the current user's local time for start or end of the day of that date is used.
- If possible, the actual sprint start and completion times should be used as defined in \#\#\#AGILE-399
**Technical notes**
**Permissions and visibility considerations**
- Users having the "view sprints" permission can see the sprint goal widget
**Translation considerations**
-
**Out of scope**
- Configuring the widget
- Displaying a different unit than story points (this will change with \#\#\#AGILE-198
- Showing the Enterprise banner if the users edition is not sufficient. That will be done as part of \#\#\#AGILE-398