# Feature AGILE-304 - Work package tables (completed, unfinished, added, removed) on sprint report page

Project: Stream agile
Status: in test
URL: https://community.openproject.org/work_packages/AGILE-304

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 13 |
| 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

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Backlogs |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=250-12918&t=MUEBFP23fLVPrXBe-1 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Ivana Šugić |
| Accountable |  |
| Product manager |  |
| Developers | Ivan Kuchin |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Follows <mention class="mention" data-id="AGILE-296" data-type="work_package" data-text="###AGILE-296">###AGILE-296</mention>

**As** an agile user  
**I want to** have tables listing work packages of different criteria   
**so that** I can understand the sprint's work package state in more depth

**Acceptance criteria**

  - The sprint report page has four work package tables as widgets
    
      - "Completed work ~~packages~~"
        
          - Work packages associated to the sprint that are finished
        
          - Reference date: sprint finish date or current date (earlier one)
    
      - "Unfinished work ~~packages~~"
        
          - Work packages associated to the sprint that are not finished
        
          - Reference date: sprint finish date or current date (earlier one)
    
      - "Scope increase after sprint start"
        
          - Work packages added from the sprint after the sprint start date
        
          - If the sprint start date is in the future show a blank slate stating: "Work packages will appear here after the sprint starts."
    
      - "Scope removal after sprint start"
        
          - Work packages removed from the sprint after the sprint start date
        
          - If the sprint start date is in the future show a blank slate stating: "Work packages will appear here after the sprint starts."

  - If dates are not set for the sprint, blankslates are shown.

  - Each of those work package tables are
    
      - baseline table if the reference date is a sprint start or finish date
    
      - non baseline table if the reference date is the current date

  - The widget is only displayed if the instance has an EE pro license

  - The columns in the table are:
    
      - ID
    
      - Subject
    
      - Type
    
      - Status
    
      - Assignee

Notes:

  - "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)

  - The widgets should always cover the full width

  - While the sprint start and finish dates are dates (without time zones) the current user's local time for start or end of the day of that date is used.

  - The widget will be EE (pro) only. Because of that, all users able to access the widget will have access to the baseline feature which is EE (basic).

**Technical notes**

**Permissions and visibility considerations**

  - View sprints (and by that view work packages) is required.

**Translation considerations**

**Out of scope**

  - Configuring the widgets