# Feature AGILE-296 - Sprint report page with burndown chart widget 

Project: Stream agile
Status: tested
URL: https://community.openproject.org/work_packages/AGILE-296

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 8 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-312 | Burndown blankslate offers action button to edit sprint and set dates | Implementation | needs review |  |  |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-405 | Bug | Sprint report: long titles take too much space on mobile as they are not truncated | confirmed |  | 18.0.0 |  | Modules and project features / Backlogs |
| AGILE-404 | Bug | Sprint report: breadcrumb and title overlap with long titles | confirmed |  | 18.0.0 |  | Modules and project features / Backlogs |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=0-1&t=CxY3o2NyF0XJ9kr0-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

**As** an agile user  
**I want to** have a sprint overview page with an overview of the sprint  
**so that** I can easily understand what happened in the sprint

**Acceptance criteria**

  - There is a sprint report page
    
      - The header shows:
        
          - the breadcrumb: \[Project name\] / Backlogs / \[Sprint name\] / Report
        
          - The title: \[Sprint name\] report
        
          - The status of the sprint
        
          - The dates of the sprint
    
      - A single, static widget is displayed on the page (subject to change later)
        
          - the burndown chart is moved from its full page inside the widget. Its functionality is unchanged.
            
              - \[open\] if not dates are set on the sprint, the burndown chart cannot be rendered. Do we hide the widget then completely or show a message informing the user about the need for the dates?
        
          - \[note\] The specification on this widget is still changing. It might well be that e.g. <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">\#\#\#AGILE-198</mention>will have to be taken into consideration, especially if "work" or " none" is selected as the unit.
            
              - Probably, the burndown chart will need to be able to work with those different units.

  - When on the report page, the "All sprints" menu item is selected

  - The page can be accessed:
    
      - via all sprints index page
        
          - Every row gets a ... menu at the end. The menu contains the following items:
            
              - Edit sprint - changing the name and dates will necessitate a reload of the page
            
              - Sprint report - takes the user to the sprint report
            
              - Sprint board - takes the user to the sprint board
    
      - via ... menu on sprints within the "backlog and sprints" page
        
          - The "Burndown chart" menu item will be replaced by the link to the report page (if the feature flag is active)
    
      - ~~from the sprint board~~
        
          - We currently cannot control the headers. This will only be possible with the reworked boards view.

  - The feature is hidden behind a feature flag. This is done so that additional widgets can be added one by one before it is released to the public.

**Technical notes**

  - The page will be static. There is no possibility whatsoever for the user to configure it. But the page should look like a dashboard so that a configurable dashboard can later replace it.

**Permissions and visibility considerations**

  - Users allowed to view the sprint are allowed to see the page and its contents.

**Out of scope**

  - Manipulating the report page (subject to change)

  - Show additional widgets (subject to change)

<br>