# Feature AGILE-66 - Provide velocity charts

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions | 18.0.0 |
| Sprint | Sprint 12 |
| Backlog bucket |  |
| Votes | 1 |
| List | RM Agile, Agile Reporting |
| Roadmap | 2026 Q4 |
| Relevance | Important — Required Short-Term |

## 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-479 | Bug | Velocity chart: information are incorrect when sprint is In planning mode | closed |  | 18.0.0 |  | Modules and project features / Backlogs |
| AGILE-487 | Bug | Sprint reporting: when sprint is in planning and starts today, reports show wrong number of wps | confirmed |  | 18.0.0 |  | Modules and project features / Backlogs |
| AGILE-482 | Bug | Velocity chart: story points are not bolded on two places | confirmed |  | 18.0.0 |  | Modules and project features / Backlogs |
| AGILE-488 | Bug | Velocity chart is hidden when the sprint doesn't have dates, unlike other reports that do show with blansklates | confirmed |  | 18.0.0 |  | Modules and project features / Backlogs |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=1270-11666&t=BSTVfVINX1uwi0zg-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Rosanna Sibora |
| Developers | Tobias Dillmann |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by | Black (37919), Joules (39703), Home (224196000003952096) |

## Estimates and progress

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

## Description

As an agile coach I would like to understand my teams' current velocity so that we can use the average velocity for the sprint planning in future.

**Acceptance criteria**

  - Should automatically show as a part of a sprint report (both completed and active sprints)

  - Should show past 7 sprints as a bar chart with the numbers displayed (like the charts in the Dashboard)
    
      - The last sprint (the one to the right) is the one the report page is created for. That means the widget always shows the 6 sprints before the looked at sprint and the sprint looked at. If the sprint is not completed, the values might still change. Once the sprint is completed, the values should no longer change.
        
          - The sprint name is used as a label. The name needs to be truncated if the name is long.
        
          - since there is no explicit ordering of sprints we rely on the dates to order sprints.
            
              - If sprint was started/completed, use the dates introduced with <mention class="mention" data-id="78631" data-type="work_package" data-text="###AGILE-399" data-display-id="AGILE-399">\#\#\#AGILE-399</mention>, otherwise rely on the start and finish date.
        
          - if there are less than 7 sprints, we simply show less. Meaning in the extreme, only a single sprint is shown.

  - Should compare committed number of story points and completed
    
      - The axises depict
        
          - x: sprints
            
              - \[open\] How to display long sprint names? Ideally chart.js solves this itself.
        
          - y: story points
    
      - The datasets are:
        
          - Committed: Sum of story points stored on work packages associated to the sprint when the sprint is started (button pressed)
            
              - requires <mention class="mention" data-id="78631" data-type="work_package" data-text="###AGILE-399" data-display-id="AGILE-399">\#\#\#AGILE-399</mention>
        
          - Completed: Sum of story points stored on work packages associated to the sprint when the sprint is completed (button pressed). If the sprint is not yet completed, use the current value.
            
              - requires <mention class="mention" data-id="78631" data-type="work_package" data-text="###AGILE-399" data-display-id="AGILE-399">\#\#\#AGILE-399</mention>

  - Should show a line representing the average velocity of the last 7 sprints with the number next to/on top of/over/? the line (let's discuss between design and dev what the design options are with chartjs and OP\!)

  - in addition to the bar chart we should show the following numbers within the chart
    
      - velocity of the last (looked at) sprint.
    
      - average velocity of 7 past sprints

  - If multiple active sprints are enabled for the project the velocity chart is not displayed.

  - \[open\] For all graphs: How are the graphs scrolled. Or is the whole page scrolled?
    
      - Let's stick to the current behavior also present in the Dashboard, and reach out to Julia f that doesn't work.

  - \[open\] What is displayed on hover? The dataset name and the value or nothing at all?
    
      - Since the sprint name might be too long for the graph, I'd show the sprint name and the value on hover (Julia).

**Out of scope**

  - Should be possible for a user to define the velocity chart as a widget on the project dashboard

  - Users should be able to define how many sprints they would like to see on the chart

  - What happens with multiple active sprints?

  - Can we attach semantic colors? It would be weird to have committed as green and completed as red.