# Feature AGILE-399 - Use the sprint completion date (and time) over the planned sprint end date on charts of the reporting page

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-399

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 9 |
| Backlog bucket |  |
| Votes |  |
| List | Agile Reporting |
| Roadmap | 2026 Q4 |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| AGILE-406 | Create started_at and completed_at db fields for sprints | Implementation | closed | Tobias Dillmann |  |  |

## 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 |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Rosanna Sibora |
| Developers | OP Dev Polaris Team |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a scrum master/team lead/agile report user  
**I want to** have the true sprint&#x27;s start and completion date everywhere in the sprint report  
**so that** I have accurate data about my team&#x27;s work

**Acceptance criteria**

*   the charts, etc. use&nbsp;
    
    *   if the sprint hasn&#x27;t been started (no button pressed) and no dates exist
        
        *   Nothing (and thus are not displayed) if they rely on dates (this might be different by chart)
            
    *   if the sprint hasn&#x27;t been started and the manual dates exist
        
        *   Start time: the scheduled start time
            
        *   Finish time: the scheduled finish time
            
    *   if the sprint has been started (using the button) but not completed and the scheduled completion time has not been reached yet
        
        *   Start time: time the button was pressed to start the sprint
            
        *   Finish time: The scheduled finish time.
            
    *   if the sprint has been started (using the button) but not completed and the current time is after the scheduled completion time
        
        *   Start time: time the button was pressed to start the sprint
            
        *   Finish time: Current time.
            
    *   if the sprint has been completed (using the button)
        
        *   Start time: time the button was pressed to start the sprint
            
        *   Finish time: time the button was pressed to complete the sprint
            
*   In the scenario where the current time is before the planned finish time and the sprint has not been completed charts render:
    
    *   Projections and displayed time intervals stretch to the planned finish time
        
    *   Projections begin at the current time
        
    *   the displayed time frame until the planned finish time.
        

**Technical notes**

*   <br>
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
