# Feature AGILE-484 - Display actual start and finish dates in the UI

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 13 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Tobias Dillmann |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

When a sprint is started, many places do no longer consider the planned start date, but instead use the actual start time (started\_at). The same is true for the completion. However, these factual times when a sprint was actually started and finished never show up in the web UI. This should change.

**Acceptance criteria**

*   In the all sprints table
    
    *   The value for the "start date":
        
        *    is the planned start\_date for sprints that are in planning
            
            *   a muted "(planned)" is written behind the date
                
        *   is the actual start date (started\_at) for sprints that are active or completed
            
    *   The value for the "finish date":
        
        *   is the planned finish date for sprints that are in planning or active.
            
            *   a muted "(planned)" is written behind the date
                
        *   is the actual finish date (completed\_at) for sprints that are completed
            

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/926356/content">

<br>

*   On the backlog &amp; sprints page:
    
    *   The value for the &quot;start date&quot;:
        
        *   is the planned start\_date for sprints that are in planning
            
        *   is the actual start date (started\_at) for sprints that are active or completed
            
    *   The value for the &quot;finish date&quot;:
        
        *   is the planned finish date for sprints that are in planning or active.
            
        *   is the actual finish date (completed\_at) for sprints that are completed
            
*   On the sprint report page
    
    *   The value for the &quot;start date&quot;:
        
        *   is the planned start\_date for sprints that are in planning
            
        *   is the actual start date (started\_at) for sprints that are active or completed
            
    *   The value for the &quot;finish date&quot;:
        
        *   is the planned finish date for sprints that are in planning or active.
            
        *   is the actual finish date (completed\_at) for sprints that are completed
            

<br>

**Technical notes**

*   `started_at` and `completed_at` are timestamps, while the planned dates are just dates. In the UI, we will always show the date and omit the time
    
*   \[open\] should the full timestamp be shown on mouse hover? E.g., as title attribute.
    

**Permissions and visibility considerations**

*   Nothing to consider here
    

**Out of scope**

*   <br>
    

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