# Feature AGILE-58 - Introduce burnup charts

Project: Stream agile
Status: merged
URL: https://community.openproject.org/work_packages/AGILE-58

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 13 |
| Backlog bucket |  |
| Votes |  |
| List | RM Agile, Agile Reporting |
| Roadmap | 2026 Q4 |
| 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Rosanna Sibora |
| Developers | Tobias Dillmann |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by | Tiziano (37949) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work | 30d 0h |
| Labor costs |  |

## Description

**As** an agile coach  
**I want to** have a burnup chart as a widget on the project overview and in the sprint report  
**so that** I can track the progress of a sprint (or within another defined timeline) and the scope creep.

**Acceptance criteria**

  - There is a widget called "Burnup chart" on the sprint report page.
    
      - A lot of specification for the burnup chart is shared with <mention class="mention" data-id="76439" data-type="work_package" data-text="###AGILE-308" data-display-id="AGILE-308">\#\#\#AGILE-308</mention>

  - the red line shows the work scope - for now, the work scope consists of all work packages associated to the sprint at that point in time (see out of scope for changes to this)
    
      - if the sprint scope increases the line goes up
    
      - if the scope decreases the line goes down
    
      - the end of the red line should always touch the end of the guideline

  - the green line / area shows the work completed
    
      - if wp were closed the line goes up
        
          - A wp is considered closed if it has any of the statuses configured to be closed in the backlogs project settings.
    
      - if a completed wp was removed from the sprint the line goes down
    
      - if a completed wp was reopened within the sprint the line goes down

  - there is a guideline showing a prediction for an ideal delivery
    
      - If the scope of the sprints change (reevaluation, added, removed), the guideline goal (value at the end of the sprint) is adjusted as the guideline and the work scope should have the same value at the end of the sprint.
    
      - the data series starts at the value the "work completed" data series has at the start of the sprint. This will most of the time be 0.
    
      - the data series is also adjusted time wise. 
        
          - If the sprint takes longer than the originally planned finish date, the guideline adjusts.
        
          - If the sprint takes shorter than the originally planned finish date, the guideline adjusts
        
          - This is different to how it is handled in the burndown chart. 

  - Non-working days are displayed as grey areas

  - while within the sprint the red line should be dotted for future dates indicating that it's only a scope prediction. This is its own data series.

  - The dates follow the pattern defined in <mention class="mention" data-id="78631" data-type="work_package" data-text="###AGILE-399" data-display-id="AGILE-399">\#\#\#AGILE-399</mention>

  - Initially, the unit on the y-axis is in story points. This is subject to change with <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">\#\#\#AGILE-198</mention>

**Out of scope**

  - in the future users should be able to add burnup charts also as a widget to the dashboard and define a certain scope (e.g. all wp within a project or wp associated with a certain component) instead of a sprint scope and a custom timeline.

  - \[open question\]: would it be possible to show data points at changes so that users can hover over it and see which wp were added or removed directly within the chart? Both for the green and red line